Triple
T160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Institute of Technology |
E3
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | north bank of the Charles River |
—
|
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: north bank of the Charles River | Statement: [Massachusetts Institute of Technology, locatedOn, north bank of the Charles River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOn Context triple: [Massachusetts Institute of Technology, locatedOn, north bank of the Charles River]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
headquartersLocation
Indicates the place where an organization’s main administrative center or principal office is located.
-
C.
placeOfBirth
Indicates the location where a person or other entity was born.
-
D.
placeOfDeath
Indicates the location where an entity (typically a person or animal) died.
-
E.
areaServed
Indicates the geographic region or jurisdiction within which a service, organization, or activity is provided or applicable.
- 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_69a222a954e48190b48f126a67485661 |
completed | Feb. 27, 2026, 11:03 p.m. |
| NER | Named-entity recognition | batch_69a228187e888190b2bb2aee9a69b61b |
completed | Feb. 27, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69a226e6f58881908808f6985f779c3c |
completed | Feb. 27, 2026, 11:21 p.m. |
Created at: Feb. 27, 2026, 11:04 p.m.