Triple
T2837456
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | İZBAN |
E62384
|
entity |
| Predicate | lineOrientation |
P42939
|
FINISHED |
| Object | north–south 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: north–south axis | Statement: [İZBAN, lineOrientation, north–south axis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lineOrientation Context triple: [İZBAN, lineOrientation, north–south axis]
-
A.
lineType
Indicates the specific category or style of a line used in a representation, such as its function or visual convention.
-
B.
lineElement
Indicates a relationship where something functions as, or is identified as, an element or segment of a line within a larger linear structure or representation.
-
C.
lineStandard
Indicates that one entity is a standard or reference specification that defines or governs the characteristics or requirements of a particular line (such as a product line, production line, or service line).
-
D.
lineSymbol
Indicates that one entity is used as a line-style or line-representation symbol for another entity.
-
E.
lineTerminusDirection
Indicates the directional orientation or bearing at which a line segment or route terminates at its endpoint.
- 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_69ab4c3c39188190955b9c49d98463d8 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdeede0488190a9782f55b57559ee |
completed | March 7, 2026, 8:16 a.m. |
| PD | Predicate disambiguation | batch_69abdd0ce8b08190ba28c192988f38ce |
completed | March 7, 2026, 8:08 a.m. |
| PDg | Predicate description generation | batch_69abde4895dc819097c396c5d31ac1d1 |
completed | March 7, 2026, 8:14 a.m. |
Created at: March 6, 2026, 10:01 p.m.