Triple
T33775159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarth |
E865495
|
entity |
| Predicate | hasLord |
P47636
|
FINISHED |
| Object | Lord of Tarth |
—
|
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: Lord of Tarth | Statement: [Tarth, hasLord, Lord of Tarth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLord Context triple: [Tarth, hasLord, Lord of Tarth]
-
A.
lordOf
chosen
Indicates that one entity holds lordship, authority, or dominion over another entity.
-
B.
hasLordSpeaker
Indicates that one entity serves as the Lord Speaker (presiding officer) of another entity, typically a parliamentary or legislative body.
-
C.
firstKnownLord
Indicates that the subject is the earliest historically or canonically recorded lord associated with the object.
-
D.
hasLordMayor
Indicates that an entity holds the position or role of Lord Mayor for another entity (typically a city or municipality).
-
E.
hasDominion
Indicates that one entity holds authority, control, or governing power over another entity or domain.
- 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_69f3498df6f88190bf9647ea4e4a956e |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 1, 2026, 1:45 a.m.