Triple
T31421421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A7 north–south corridor |
E801539
|
entity |
| Predicate | hasAxisDirection |
P156971
|
FINISHED |
| Object | north–south |
—
|
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 | Statement: [A7 north–south corridor, hasAxisDirection, north–south]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAxisDirection Context triple: [A7 north–south corridor, hasAxisDirection, north–south]
-
A.
isAxisDirection
chosen
Indicates that one direction is aligned with or corresponds to a principal axis (such as x, y, or z) in a given coordinate system.
-
B.
hasAxisConfiguration
Indicates that one entity specifies or defines the axis arrangement, orientation, or setup used by another entity.
-
C.
hasAxisCount
Indicates that an entity is associated with a specified number of axes.
-
D.
isOnAxis
Indicates that one entity lies directly along a specified axis or reference line defined by another entity or coordinate system.
-
E.
usesAxis
Indicates that one entity employs or relies on another entity as a reference axis or basis for orientation, measurement, or organization.
- 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_69f348c26f048190b4adadd71b4596c5 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:48 p.m.