Triple
T34448866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yeats family by marriage |
E884304
|
entity |
| Predicate | primaryGeographicContext |
P1103
|
FINISHED |
| Object | Dublin |
E9406
|
NE FINISHED |
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: Dublin | Statement: [Yeats family by marriage, primaryGeographicContext, Dublin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryGeographicContext Context triple: [Yeats family by marriage, primaryGeographicContext, Dublin]
-
A.
geographicContext
Indicates that one entity is situated within, associated with, or characterized by the geographic setting or region defined by another entity.
-
B.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
C.
secondaryGeographicFocus
Indicates a secondary or less primary geographic area that is also a focus or target of the entity’s activities, influence, or relevance.
-
D.
populationContext
Indicates the demographic or population-related setting or conditions within which an entity, event, or measurement is defined or interpreted.
-
E.
primaryTerritory
chosen
Indicates that a specified area or region is the main or most important territory associated with an entity.
- F. None of above.
Provenance (4 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_69f349c607688190b553539d14901a35 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a37792b19008190895e3d5da5a3e685 |
completed | June 21, 2026, 5:39 a.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 2 a.m.