Triple
T19889665
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mrs Lyons |
E477993
|
entity |
| Predicate | movesHouseTo |
P67543
|
FINISHED |
| Object | the countryside |
—
|
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: the countryside | Statement: [Mrs Lyons, movesHouseTo, the countryside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movesHouseTo Context triple: [Mrs Lyons, movesHouseTo, the countryside]
-
A.
movedPremises
chosen
Indicates that an entity has changed its location or base of operations from one set of premises to another.
-
B.
movedCommunityTo
Indicates that an entity caused a community or group to relocate from one place to another.
-
C.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
D.
laterResidenceShiftOf
Indicates that one residence shift event occurs chronologically after another residence shift event for the same entity.
-
E.
mayRelocateTo
Indicates that an entity has the possibility or permission to move or be moved from its current location to another specified location.
- 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_69d8e51f32b08190b3687f4f60353250 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6590ce9f48190a51c0e5ecc828a06 |
completed | April 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.