Triple
T18589495
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutz family |
E454324
|
entity |
| Predicate | movedInto |
P67543
|
FINISHED |
| Object | 112 Ocean Avenue in December 1975 |
—
|
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: 112 Ocean Avenue in December 1975 | Statement: [Lutz family, movedInto, 112 Ocean Avenue in December 1975]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: movedInto Context triple: [Lutz family, movedInto, 112 Ocean Avenue in December 1975]
-
A.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
-
B.
movedPremises
chosen
Indicates that an entity has changed its location or base of operations from one set of premises to another.
-
C.
movedCommunityTo
Indicates that an entity caused a community or group to relocate from one place to another.
-
D.
movedBy
Indicates that an entity changes position or location as a result of another entity’s action or influence.
-
E.
relocatedWithin
Indicates that an entity has moved from one location to another while remaining within the same broader area or jurisdiction.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545b4a2a0819098047ee81278bd9d |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478c98d4c81909d37a0e72c6e7bd0 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.