Triple
T25966579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIT MacGregor House |
E645686
|
entity |
| Predicate | hasMoveIn |
P155849
|
FINISHED |
| Object | MIT fall term |
—
|
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: MIT fall term | Statement: [MIT MacGregor House, hasMoveIn, MIT fall term]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMoveIn Context triple: [MIT MacGregor House, hasMoveIn, MIT fall term]
-
A.
movedIn
chosen
Indicates that an entity has taken up residence or established occupancy at a new location or dwelling.
-
B.
movedOn
Indicates that an entity changed its position or location from one place to another at some point in time.
-
C.
hasMovementLegacy
Indicates that an entity carries forward, preserves, or significantly influences the ongoing impact, traditions, or ideals of a particular movement.
-
D.
usesMove
Indicates that an entity performs or executes a specific move or action.
-
E.
movedFor
Indicates that one entity changed its location or position for the benefit, purpose, or in response to another entity.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 22, 2026, 8:48 a.m.