Triple
T33112192
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Edain |
E847358
|
entity |
| Predicate | secondHouse |
P12817
|
FINISHED |
| Object | House of Haleth |
—
|
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: House of Haleth | Statement: [Edain, secondHouse, House of Haleth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondHouse Context triple: [Edain, secondHouse, House of Haleth]
-
A.
secondHolderHouse
Indicates that an entity is the second person or party to hold or occupy a particular house or dwelling.
-
B.
secondHouseRole
Indicates that an entity serves as the second most prominent or secondary role within a particular house or household.
-
C.
house2
chosen
Indicates a relationship where one entity is a secondary, related, or alternative house associated with another entity.
-
D.
thirdHouse
Indicates that one entity is the third house in a sequence or ordering relative to another entity.
-
E.
secondHolder
Indicates that an entity is the second person or party to hold or possess a particular item, role, title, or position in a sequence.
- 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_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
Created at: May 1, 2026, 1:27 a.m.