Triple
T22721484
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Q Line |
E561872
|
entity |
| Predicate | providesConnectionType |
P1374
|
FINISHED |
| Object | north–south connections |
—
|
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 connections | Statement: [Q Line, providesConnectionType, north–south connections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: providesConnectionType Context triple: [Q Line, providesConnectionType, north–south connections]
-
A.
providesNetworkType
Indicates that one entity supplies or specifies the type of network associated with another entity.
-
B.
connectorType
chosen
Indicates the specific kind or category of connection interface that links two entities.
-
C.
connectorTypeDesignation
Indicates the specific type or classification assigned to a connector within a connection or interface relationship.
-
D.
connectivityMode
Indicates how two or more entities are linked or able to communicate with each other, such as the type or method of connection used between them.
-
E.
compatibleConnection
Indicates that two entities can be connected or used together without conflict, supporting proper operation or interaction.
- 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17911a4fc81908a125209aea77e22 |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:19 p.m.