Triple
T17958950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matrimandir |
E449024
|
entity |
| Predicate | positionInTownship |
P82773
|
FINISHED |
| Object | center of Auroville |
—
|
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: center of Auroville | Statement: [Matrimandir, positionInTownship, center of Auroville]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInTownship Context triple: [Matrimandir, positionInTownship, center of Auroville]
-
A.
positionInBorough
Indicates that one entity is located within or belongs to the geographic area of a specific borough.
-
B.
positionEstablishedIn
Indicates the point in time or event when a particular position, role, or office was formally created or instituted.
-
C.
propertyLocation
Indicates the geographical place or address where a property is situated or found.
-
D.
positionOnTerritory
Indicates that one entity occupies or is located at a specific position within the spatial extent of another entity’s territory.
-
E.
locatedInPlannedTown
chosen
Indicates that an entity is situated within the boundaries of a town that has been deliberately planned or designed rather than having developed organically.
- 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_69d8b9f8cca8819099836916c56b7c95 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b130b7a081908542a3bc6dab5842 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8f2bd088190b1e22ad4d9cc8b13 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.