Triple
T36556454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Riddermark |
E901709
|
entity |
| Predicate | oathRelationship |
P185853
|
FINISHED |
| Object | Oath of Eorl with Gondor |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Oath of Eorl with Gondor | Statement: [The Riddermark, oathRelationship, Oath of Eorl with Gondor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oathRelationship Context triple: [The Riddermark, oathRelationship, Oath of Eorl with Gondor]
-
A.
inRelationshipWith
Indicates that two entities are mutually involved in a defined personal, romantic, or partnership relationship with each other.
-
B.
haveRelationshipWith
Indicates that one entity is in some form of defined relationship or association with another entity.
-
C.
relationshipToBond
Indicates the specific type of personal, familial, or professional relationship an entity has to the person named Bond.
-
D.
addressesRelationship
Indicates that one entity directs communication, remarks, or attention specifically toward another entity.
-
E.
establishedRelationship
Indicates that a formal, recognized relationship has been created and is now in effect between the referenced entities.
- F. None of above. chosen
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f76e634e9481908c9ba1b87ab87c26 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.