Triple
T3402134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songjiazhuang station |
E71678
|
entity |
| Predicate | locatedInNetworkSector |
P14543
|
FINISHED |
| Object | southern part of Beijing Subway network |
—
|
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: southern part of Beijing Subway network | Statement: [Songjiazhuang station, locatedInNetworkSector, southern part of Beijing Subway network]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInNetworkSector Context triple: [Songjiazhuang station, locatedInNetworkSector, southern part of Beijing Subway network]
-
A.
positionInNetwork
Indicates the specific role or location an entity occupies within a network’s structure or topology.
-
B.
networkSection
chosen
Indicates that one entity represents a specific section, segment, or subdivision within a larger network structure.
-
C.
networkServed
Indicates that a network provides connectivity or services to a particular entity or set of entities.
-
D.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
E.
operatesInSegment
Indicates that an entity conducts its activities or provides its services within a specified market or operational segment.
- 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_69ad85aac4808190a092c9cc8911f584 |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb8c96d7c8190a1f9d035996f79e3 |
completed | March 8, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69adadfa73ac8190a163f93e88d217f8 |
completed | March 8, 2026, 5:12 p.m. |
Created at: March 8, 2026, 3:14 p.m.