Triple
T7253113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Magnetic South Pole |
E157652
|
entity |
| Predicate | fieldLineOrientation |
P42939
|
FINISHED |
| Object | field lines emerge from Earth |
—
|
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: field lines emerge from Earth | Statement: [Magnetic South Pole, fieldLineOrientation, field lines emerge from Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fieldLineOrientation Context triple: [Magnetic South Pole, fieldLineOrientation, field lines emerge from Earth]
-
A.
lineOrientation
chosen
Indicates the directional alignment or angle of a line relative to a reference frame or axis.
-
B.
yardLine
Indicates the specific position on a football field, measured in yards from a reference goal line, where a play or event occurs.
-
C.
frontLineDirection
Indicates the primary orientation or bearing in which the front line of a conflict, formation, or boundary is facing or advancing.
-
D.
fieldSide
Indicates the relative side or position of something with respect to a defined field or playing area.
-
E.
lineCorridor
Indicates that one entity is a corridor represented or approximated by a line, typically modeling a narrow passageway or path between areas.
- 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_69c6882d81d4819085f7ff862951ee4f |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6ea9d41908190bb76c6a5b9d5b1a2 |
completed | March 27, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69c6e7666ffc81908bf643d8257e6337 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:56 p.m.