Triple
T28996894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIThenge |
E736188
|
entity |
| Predicate | occursInBuilding |
P168640
|
FINISHED |
| Object | MIT Building 7 to Building 10 axis |
—
|
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 Building 7 to Building 10 axis | Statement: [MIThenge, occursInBuilding, MIT Building 7 to Building 10 axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occursInBuilding Context triple: [MIThenge, occursInBuilding, MIT Building 7 to Building 10 axis]
-
A.
isLocatedInBuilding
Indicates that one entity is physically situated within or inside the structure of a particular building.
-
B.
locatedInBuildingWithFeature
Indicates that something is located in a building that possesses a specified feature or characteristic.
-
C.
tookPlaceInBuilding
Indicates that an event or action occurred within the physical premises of a specific building.
-
D.
locatedInBuildingUsedAs
Indicates that something is located inside a building that is being used for a specified purpose or function.
-
E.
hostedInBuilding
Indicates that an event, activity, or service takes place within or is accommodated inside a specific building.
- F. None of above. chosen
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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f67595fa7c8190b6e9f7a8c700dd97 |
completed | May 2, 2026, 10:07 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f674df80b08190adb7f7531083bbb1 |
completed | May 2, 2026, 10:04 p.m. |
Created at: April 28, 2026, 9:31 a.m.