Triple
T29544018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohirric |
E749580
|
entity |
| Predicate | hasNotableNameElement |
P150492
|
FINISHED |
| Object | Eorl |
—
|
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: Eorl | Statement: [Rohirric, hasNotableNameElement, Eorl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNotableNameElement Context triple: [Rohirric, hasNotableNameElement, Eorl]
-
A.
isNotableNameOf
Indicates that a name is widely recognized or distinguished as a significant identifier for the referenced entity.
-
B.
hasProperNameElement
chosen
Indicates that an entity’s proper name includes a specific component (such as a word, phrase, or segment) as one of its constituent elements.
-
C.
hasNotablePropertyNamedAfter
Indicates that an entity possesses a notable property or attribute that is named in honor of, or derived from, another entity.
-
D.
hasNotableEventName
Indicates that an entity is associated with a notable event identified by a specific name.
-
E.
hasNotableNamesakeType
Indicates that an entity has a notable namesake of a specified type (such as a person, place, or work) that shares its name.
- 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_69f0bd48691081908cecad39bac591e0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69ffc7b4c7f88190b6357a44e7f0940f |
completed | May 9, 2026, 11:48 p.m. |
| PD | Predicate disambiguation | batch_69ffc755f09c8190995ca00d97336988 |
completed | May 9, 2026, 11:46 p.m. |
Created at: April 28, 2026, 5:05 p.m.