Triple
T34672250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4R |
E890405
|
entity |
| Predicate | hasUnitForHeading |
P192596
|
FINISHED |
| Object | degrees magnetic |
—
|
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: degrees magnetic | Statement: [4R, hasUnitForHeading, degrees magnetic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUnitForHeading Context triple: [4R, hasUnitForHeading, degrees magnetic]
-
A.
hasHeading
Indicates that one entity serves as a heading or title for another entity.
-
B.
hasUnitIn
Indicates that one entity is contained or measured within another as a unit, specifying a unit-of-measure or component relationship.
-
C.
hasUnitOf
Indicates that a quantity, measurement, or value is expressed in terms of a specific unit.
-
D.
hasUnitClass
Indicates that an entity is associated with, or categorized under, a particular unit classification or type.
-
E.
hasUnitStructure
Indicates that an entity possesses a specific internal organization or arrangement that defines its structural composition.
- 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_69f349d9c59481908b36baa0be093aea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd19f791f48190bbb6f6047f9ddc59 |
completed | May 7, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69fd0df365948190bc9bfc7ffd46acd8 |
completed | May 7, 2026, 10:10 p.m. |
| PDg | Predicate description generation | batch_69fd19f6a7888190aa7eee2b87687c53 |
completed | May 7, 2026, 11:02 p.m. |
Created at: May 1, 2026, 2:05 a.m.