Triple
T34698802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | D2 motorway |
E1000302
|
entity |
| Predicate | connectsToNetworkIn |
P128636
|
FINISHED |
| Object | Czech Republic |
—
|
NE NERFINISHED |
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: Czech Republic | Statement: [D2 motorway, connectsToNetworkIn, Czech Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: connectsToNetworkIn Context triple: [D2 motorway, connectsToNetworkIn, Czech Republic]
-
A.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
B.
inNetwork
Indicates that one entity is within the same defined network, system, or coverage group as another entity, such that network-based interactions or benefits apply between them.
-
C.
isPartOfNetworkEnd
Indicates that an entity functions as a terminal or boundary component within a larger network structure or system.
-
D.
isPartOfNetworkServing
Indicates that one entity functions as a component within, or is supported by, a particular network that provides services to it or through it.
-
E.
intendedNetwork
chosen
Indicates the network that an entity is planned, designed, or expected to connect to or operate within.
- 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_69f76dab937881909c86f1b9ad50445f |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff64b957bc81908afbc5914234a8ea |
completed | May 9, 2026, 4:45 p.m. |
| PD | Predicate disambiguation | batch_69ff6446593c81909173e296eea2590c |
completed | May 9, 2026, 4:43 p.m. |
Created at: May 3, 2026, 3:59 p.m.