Triple
T33217183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Longbeards |
E850318
|
entity |
| Predicate | laterRefuge |
P101706
|
FINISHED |
| Object | The Iron Hills |
—
|
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: The Iron Hills | Statement: [Longbeards, laterRefuge, The Iron Hills]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRefuge Context triple: [Longbeards, laterRefuge, The Iron Hills]
-
A.
takenAsRefugeBy
chosen
Indicates that one entity is used or relied upon by another entity as a place or source of safety, protection, or refuge.
-
B.
closestRefuge
Indicates that one location serves as the nearest place of safety or shelter relative to another specified point or entity.
-
C.
designatedAsRefuge
Indicates that an entity has been officially assigned or recognized as a refuge or place of protection.
-
D.
wasRefugee
Indicates that an entity previously lived as a refugee, having been forced to leave their home country due to conflict, persecution, or disaster.
-
E.
timeOfRefuge
Indicates the specific time period during which an entity is given or is in a state of refuge or protection.
- 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_69f3496083dc8190b229bb6932dc548b |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffcb5536d88190bfc2e00b854cacfb |
completed | May 10, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69ffc900c2a081909dea04aa60566923 |
completed | May 9, 2026, 11:53 p.m. |
Created at: May 1, 2026, 1:30 a.m.