Triple
T12742154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Unnatamsa Yantra |
E304513
|
entity |
| Predicate | coordinateMeasured |
P106667
|
FINISHED |
| Object | altitude |
—
|
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: altitude | Statement: [Unnatamsa Yantra, coordinateMeasured, altitude]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateMeasured Context triple: [Unnatamsa Yantra, coordinateMeasured, altitude]
-
A.
coordinateOn
Indicates that two or more entities work together to organize, align, or manage a shared activity, process, or objective.
-
B.
coordinates
Indicates that one entity organizes, directs, or harmonizes the actions or efforts of another entity or group to achieve a unified outcome.
-
C.
coordinateUnit
Indicates that one unit serves as a coordinate or reference unit relative to another in a measurement, spatial, or organizational context.
-
D.
coordinatesWith
Indicates that one entity works together with another in an organized or synchronized manner to achieve a shared or compatible outcome.
-
E.
measuredAlong
Indicates that a measurement is taken or defined with respect to a specific direction, axis, path, or dimension.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96d89ea70819098c470344f172167 |
completed | April 10, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69d96406e97c8190b79081039847115c |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:26 p.m.