Triple
T33112662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Telcontar |
E847370
|
entity |
| Predicate | namedAfterEpithetOf |
P12247
|
FINISHED |
| Object | Aragorn II Elessar |
—
|
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: Aragorn II Elessar | Statement: [Telcontar, namedAfterEpithetOf, Aragorn II Elessar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: namedAfterEpithetOf Context triple: [Telcontar, namedAfterEpithetOf, Aragorn II Elessar]
-
A.
epithetAppliedBy
Indicates that a particular epithet or descriptive label is used or assigned by a specific agent to a target entity.
-
B.
epithetOrTitle
Indicates that one entity serves as an epithet, honorific, or formal title used to designate or characterize another entity.
-
C.
namedAccordingTo
Indicates that one entity is given a name that follows, references, or is derived from another entity or source.
-
D.
honorificEponym
chosen
Indicates that one entity serves as an honorific namesake for another, typically recognizing or commemorating the person or entity in whose honor something is named.
-
E.
eponymFor
Indicates that one entity gives its name to another entity, which is then named after it.
- F. None of above.
Provenance (3 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_69f3495751a081909850af5843da40dc |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:27 a.m.