Triple
T28996832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIThenge |
E736187
|
entity |
| Predicate | typicalLocationWithinMIT |
P203256
|
FINISHED |
| Object | Infinite Corridor |
—
|
NE NERFINISHED |
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: Infinite Corridor | Statement: [MIThenge, typicalLocationWithinMIT, Infinite Corridor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLocationWithinMIT Context triple: [MIThenge, typicalLocationWithinMIT, Infinite Corridor]
-
A.
mainLocationWithinBoston
Indicates that the primary or central location of an entity is situated within the geographic boundaries of Boston.
-
B.
memberInstitutionLocation
Indicates that a member institution is located in, or associated with, a specific geographic place or address.
-
C.
campusLocationRelativeToColumbia
Indicates the spatial relationship of a campus’s location relative to Columbia (e.g., where the campus is situated in relation to Columbia).
-
D.
ManhattanPortalLocatedIn
Indicates that a specific portal or gateway is situated within the geographic area of Manhattan.
-
E.
mainLocationWithinSalem
Indicates that the primary or central location of an entity is situated within the geographic boundaries of Salem.
- 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_6a0143a4ab3c8190a240b0facfe130a9 |
completed | May 11, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_6a01426b2d4481908654bfa4a02c457d |
completed | May 11, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_6a0143a400f881909599405b47dc1c78 |
completed | May 11, 2026, 2:49 a.m. |
Created at: April 28, 2026, 9:31 a.m.