Triple
T26592991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baraut |
E667409
|
entity |
| Predicate | pinpointLocation |
P36479
|
FINISHED |
| Object | northern India |
—
|
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: northern India | Statement: [Baraut, pinpointLocation, northern India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pinpointLocation Context triple: [Baraut, pinpointLocation, northern India]
-
A.
coordinateLocation
Indicates that an entity is located at, or associated with, a specific geographic coordinate or set of coordinates.
-
B.
mapLocation
chosen
Indicates a relationship where an entity is associated with a specific position or area on a map.
-
C.
captureLocation
Indicates the place where an entity or event is captured, recorded, or taken.
-
D.
deltaLocation
Indicates a change or difference between two locations, typically specifying how one location has shifted relative to another.
-
E.
objectLocation
Indicates that one entity is located at, in, or on another entity or spatial region.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f61526a8ac8190bd40968b613985be |
completed | May 2, 2026, 3:15 p.m. |
| PD | Predicate disambiguation | batch_69f602d7b1b0819095ddd3b5169f8ce2 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 27, 2026, 2:09 a.m.