Triple
T33836987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 安定门 |
E867258
|
entity |
| Predicate | 在城市交通中的作用 |
P44762
|
FINISHED |
| Object | 连接旧城与北部城区的重要通道 |
—
|
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: 连接旧城与北部城区的重要通道 | Statement: [安定门, 在城市交通中的作用, 连接旧城与北部城区的重要通道]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 在城市交通中的作用 Context triple: [安定门, 在城市交通中的作用, 连接旧城与北部城区的重要通道]
-
A.
transportationImpact
Indicates how one entity’s transportation-related activities or characteristics affect another entity or the surrounding environment.
-
B.
usedTransportationInfrastructure
Indicates that an entity made use of some form of transportation infrastructure (such as roads, railways, or ports) to enable movement or transit.
-
C.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
D.
facilitatesTrafficFlowBetween
chosen
Indicates that one entity enables, supports, or improves the movement of traffic between two other entities or locations.
-
E.
hasMajorTransportationRole
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
- 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_69f34992ad40819087760ed939bd2a7a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7002f38308190af948b97a35a5b09 |
completed | May 3, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69f6fc59518081908b0275f47721d561 |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 1:47 a.m.