Triple
T37277055
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A-1 |
E924673
|
entity |
| Predicate | relativeOrderOnLine |
—
|
GENERATED |
| Object | first station on Line M1 from the south |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeOrderOnLine Context triple: [A-1, relativeOrderOnLine, first station on Line M1 from the south]
-
A.
orderOf
chosen
Indicates that one entity is arranged, ranked, or sequenced before or after another according to a specified ordering criterion.
-
B.
linkedOrder
Indicates that one order is associated with or connected to another order in a defined relationship.
-
C.
confersOrder
Indicates that one entity formally bestows or grants an order, rank, or honorific distinction upon another entity.
-
D.
relativePositioning
Indicates how one entity is spatially arranged or located in relation to another entity.
-
E.
joinedOrderOf
Indicates that an entity became a member of, or formally joined, a particular order or organization.
- F. None of above.
Provenance (1 batch)
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_69f76eacdd8c819094080d3991e6d37c |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:16 p.m.