Triple
T36725855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eloise Turner |
E907193
|
entity |
| Predicate | livesWithAtStart |
P127021
|
FINISHED |
| Object | her grandmother in Cornwall |
—
|
LITERAL 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: her grandmother in Cornwall | Statement: [Eloise Turner, livesWithAtStart, her grandmother in Cornwall]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livesWithAtStart Context triple: [Eloise Turner, livesWithAtStart, her grandmother in Cornwall]
-
A.
livedWith
Indicates that two entities shared the same residence or household for a period of time.
-
B.
livesWithAtBeginning
chosen
Indicates that one entity is living together with another entity at the initial or starting point of the considered time period or event.
-
C.
residenceAtStartOfFilm
Indicates the place where a person or character is living at the beginning of the film.
-
D.
livesUnder
Indicates that one entity resides beneath or is domiciled in a lower hierarchical or physical level relative to another entity.
-
E.
hasFamilyHomeAt
Indicates that an entity has its family residence or primary household located at a specified place.
- 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_69f76e746e4c8190a0d05cc6d57a643e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c9f5a8848190ba956ff27f44e396 |
completed | May 3, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f7c8999a348190abc1895eaa6e036d |
completed | May 3, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:12 p.m.