Triple
T36549981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marcho and Blanco |
E901233
|
entity |
| Predicate | residenceFounded |
P127246
|
FINISHED |
| Object | The Shire |
E261162
|
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: The Shire | Statement: [Marcho and Blanco, residenceFounded, The Shire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: residenceFounded Context triple: [Marcho and Blanco, residenceFounded, The Shire]
-
A.
foundedAsResidenceOf
chosen
Indicates that something was originally established or created to serve as the residence of a particular person or group.
-
B.
placeFounded
Indicates the location where an entity (such as an organization or institution) was originally established or founded.
-
C.
colonyFounded
Indicates that an entity established or created a colony at a particular time or place.
-
D.
cityFounded
Indicates that a particular city was established or came into existence at a specific time or by a specific founding event or agent.
-
E.
isFoundedOn
Indicates that one entity is established, created, or based upon another entity as its foundational source or principle.
- 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_69f76e61217081908b79d610fe67b013 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39e6e617188190b48c3026dc6f70c5 |
completed | June 23, 2026, 1:52 a.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:11 p.m.