Triple
T8688477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Earth parallels system |
E206224
|
entity |
| Predicate | coordinateAxisName |
P84195
|
FINISHED |
| Object | latitude axis |
—
|
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: latitude axis | Statement: [Earth parallels system, coordinateAxisName, latitude axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coordinateAxisName Context triple: [Earth parallels system, coordinateAxisName, latitude axis]
-
A.
coordinateAxis
Indicates that one entity serves as a reference axis or directional basis for positioning, measuring, or orienting another entity in a coordinate system.
-
B.
transportAxis
Indicates a directional path or axis along which something is transported or moved from one location to another.
-
C.
coordinateSymbols
Indicates a relationship where one symbol is aligned or matched with another symbol in a coordinated or corresponding way.
-
D.
primaryAxisUnits
Indicates the units of measurement used along the primary axis in a coordinate system, chart, or spatial reference.
-
E.
coordinateSystem
Indicates that one entity defines or uses a particular spatial or reference coordinate system in relation to another entity.
- 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_69ca835481fc819084e33d3bc883bfa6 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc57334b0c8190903a5a1784e74791 |
completed | March 31, 2026, 11:22 p.m. |
| PD | Predicate disambiguation | batch_69cc4569f9048190b9c86b4c81103d35 |
completed | March 31, 2026, 10:06 p.m. |
| PDg | Predicate description generation | batch_69cc483f06f48190879f4702c8b4ed00 |
completed | March 31, 2026, 10:18 p.m. |
Created at: March 30, 2026, 6:33 p.m.