Triple
T7946945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BJT |
E184520
|
entity |
| Predicate | basedOnMeridian |
P6025
|
FINISHED |
| Object | 120th meridian east |
—
|
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: 120th meridian east | Statement: [BJT, basedOnMeridian, 120th meridian east]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnMeridian Context triple: [BJT, basedOnMeridian, 120th meridian east]
-
A.
referenceMeridian
chosen
Indicates that one location, measurement, or coordinate system is defined or interpreted relative to a specified meridian used as its longitudinal reference.
-
B.
establishedMeridianDistance
Indicates that one entity has determined or set the longitudinal (meridian) distance relative to another reference entity.
-
C.
hasMeridianFunction
Indicates a functional relationship in which a meridian performs, supports, or influences a specific physiological or energetic role.
-
D.
principalMeridianState
Indicates the association between a principal meridian and the state in which that meridian is officially used or defined.
-
E.
basedOnBy
Indicates that one entity is derived from, justified by, or constructed using another entity as its source, foundation, or reference.
- 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_69ca8291c2008190b1b8832c87814bcf |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3b2abdbc819085ae53826d36af3b |
completed | March 31, 2026, 3:10 a.m. |
| PD | Predicate disambiguation | batch_69cae93526d081909303265bf60419fd |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:09 p.m.