Triple
T33810844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S.T.S. High School |
E866525
|
entity |
| Predicate | locatedInUniversityTown |
P163391
|
FINISHED |
| Object | Aligarh |
E93124
|
NE 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: Aligarh | Statement: [S.T.S. High School, locatedInUniversityTown, Aligarh]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInUniversityTown Context triple: [S.T.S. High School, locatedInUniversityTown, Aligarh]
-
A.
containsUniversityCity
Indicates that a given region or area includes within its boundaries a city that hosts a university.
-
B.
universityLocatedIn
Indicates that a university is situated within or associated with a specific geographic location or administrative region.
-
C.
situatedInTown
chosen
Indicates that one entity is located within the geographical or administrative boundaries of a specific town.
-
D.
locatedInHubOf
Indicates that one entity is situated within the central hub or core area associated with another entity.
-
E.
isUniversitySatelliteTownOf
Indicates that a town primarily exists to serve and support a nearby university, functioning as its dependent or satellite community.
- F. None of above.
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_69f349911a8c81908478662194b23d8c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a037e0953908190b2930b3c06a40129 |
completed | May 12, 2026, 7:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3718116c9881908b482f0ea872d1c3 |
completed | June 20, 2026, 10:45 p.m. |
| PD | Predicate disambiguation | batch_6a0379f6c3308190b954f7810214ceed |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:46 a.m.