Triple
T5723145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dual Contracts |
E126196
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public transit agreement |
C16214
|
CONCEPT FINISHED |
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public transit agreement Context triple: [Dual Contracts, instanceOf, public transit agreement]
-
A.
transport infrastructure agreement
chosen
A transport infrastructure agreement is a formal contract between parties that defines the responsibilities, funding, timelines, and performance standards for planning, building, operating, or maintaining transportation facilities such as roads, railways, ports, or airports.
-
B.
public transit route
A public transit route is a predefined path with designated stops and schedules along which public transportation vehicles (such as buses, trams, or trains) operate to move passengers between locations.
-
C.
international agreement
An international agreement is a formal, negotiated arrangement between two or more sovereign states or international organizations that creates binding obligations under international law.
-
D.
European transport agreement
A European transport agreement is a formal, often multilateral, accord between European states that harmonizes rules, standards, and procedures for cross-border transportation of goods and passengers to ensure safety, efficiency, and legal consistency.
-
E.
public transit board
A public transit board is a governing body responsible for overseeing, setting policy for, and making strategic decisions about a region’s public transportation system.
- 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_69c0082f723881908ce8bb13a0c0f8b7 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:46 p.m.