Triple
T38240447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brightroar |
E1013746
|
entity |
| Predicate | lostDuringExpeditionOf |
P64517
|
FINISHED |
| Object | King Tommen II Lannister |
—
|
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: King Tommen II Lannister | Statement: [Brightroar, lostDuringExpeditionOf, King Tommen II Lannister]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lostDuringExpeditionOf Context triple: [Brightroar, lostDuringExpeditionOf, King Tommen II Lannister]
-
A.
lostDuring
chosen
Indicates that something ceased to be in possession or was no longer retained while a particular event, process, or time period was occurring.
-
B.
lostAfterDiscovery
Indicates that something ceased to be possessed or went missing after it had already been found or discovered.
-
C.
diedDuringExpeditionTo
Indicates that an entity died while participating in or as a consequence of a specific expedition to a particular place or destination.
-
D.
lostIn
Indicates that an entity has become unable to find its way or is no longer in control or possession within a particular place, situation, or context.
-
E.
diedDuringExpeditionOn
Indicates that an entity died while participating in a specific expedition that took place on a given date.
- 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_69f76dd72a248190a5fe18db2bd1eb15 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc3321ef081908023590ba70ba0cf |
completed | May 7, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fdc6e08190b05e894c59481a0d |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:30 p.m.