Triple
T1078845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ross Dependency |
E23899
|
entity |
| Predicate | includesSectorToMeridian |
P23669
|
FINISHED |
| Object | 150° west |
—
|
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: 150° west | Statement: [Ross Dependency, includesSectorToMeridian, 150° west]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesSectorToMeridian Context triple: [Ross Dependency, includesSectorToMeridian, 150° west]
-
A.
referenceMeridian
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
B.
hasMeridianCategory
Indicates that something is classified under a specific meridian-related category or type.
-
C.
principalMeridianNumber
Indicates the specific identifying number assigned to a principal meridian used as a reference line in a land or coordinate survey system.
-
D.
principalMeridianState
Indicates the association between a principal meridian and the state in which that meridian is officially used or defined.
-
E.
moreEquatorwardIn
Indicates that one entity is located closer to the equator than another entity within a specified region or reference frame.
- 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_69a493f1ddf48190a99d54b00e99f8ce |
completed | March 1, 2026, 7:30 p.m. |
| NER | Named-entity recognition | batch_69a4b943b41481909b24050ca7e78971 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b73d9f08819093668104f129840e |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b80f0fb08190a19a50e38ae8f16c |
completed | March 1, 2026, 10:05 p.m. |
Created at: March 1, 2026, 7:42 p.m.