Triple
T25739270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M33 line |
E648168
|
entity |
| Predicate | isInNetworkType |
P3937
|
FINISHED |
| Object | urban rail |
—
|
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: urban rail | Statement: [M33 line, isInNetworkType, urban rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInNetworkType Context triple: [M33 line, isInNetworkType, urban rail]
-
A.
canUseNetworkType
Indicates that an entity is permitted or able to operate using a specified type of network.
-
B.
inUniverseNetworkType
Indicates that one entity has a specific type or category of network within a particular fictional or defined universe in relation to another entity.
-
C.
isOnNetwork
Indicates that an entity is currently connected to, accessible through, or operating within a specified network.
-
D.
providesNetworkType
Indicates that one entity supplies or specifies the type of network associated with another entity.
-
E.
networkType
chosen
Indicates the category or kind of network associated with or used by an entity (e.g., wired, wireless, virtual, or specific protocol-based networks).
- 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_69e7ab306eec8190b05c312c6ab186b8 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f5fd182d30819091d64892c0a3d503 |
completed | May 2, 2026, 1:33 p.m. |
| PD | Predicate disambiguation | batch_69f4938262ac8190b41f922d0407d272 |
completed | May 1, 2026, 11:50 a.m. |
Created at: April 22, 2026, 3:39 a.m.