Triple
T35118727
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poor Fellows |
E1014110
|
entity |
| Predicate | headquartersDuringHighSparrow |
P129818
|
FINISHED |
| Object | Great Sept of Baelor |
—
|
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: Great Sept of Baelor | Statement: [Poor Fellows, headquartersDuringHighSparrow, Great Sept of Baelor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: headquartersDuringHighSparrow Context triple: [Poor Fellows, headquartersDuringHighSparrow, Great Sept of Baelor]
-
A.
headquartersDuringCampaign
chosen
Indicates the location that served as an entity’s main headquarters for the duration of a specific campaign.
-
B.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
C.
headquartersAt
Indicates that an organization’s main administrative center or primary office is located at a specified place.
-
D.
headquartersLocationInGame
Indicates the in-game location where an organization’s main base or central headquarters is situated.
-
E.
headquartersFor
Indicates that a location serves as the main administrative center or base of operations for an organization or entity.
- 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_69f76dd8b6948190aaa32b081816bd94 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:01 p.m.