Triple
T28707798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SBASE |
E729742
|
entity |
| Predicate | transportModeSupervised |
P191970
|
FINISHED |
| Object | underground 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: underground rail | Statement: [SBASE, transportModeSupervised, underground rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportModeSupervised Context triple: [SBASE, transportModeSupervised, underground rail]
-
A.
transportAssumption
Indicates an assumption that something can be transported or carried from one place or context to another.
-
B.
transportModePresent
Indicates that a particular mode of transportation is involved or available in the described context or event.
-
C.
transportModeAccess
Indicates that one entity has the ability or permission to use, reach, or be served by a particular mode of transportation.
-
D.
transportAccessType
Indicates the type or mode of transportation access available or used in a given context.
-
E.
transportModeImportant
Indicates that the mode of transport used is considered significant or plays an important role in the context of the relationship or action.
- F. None of above. chosen
Provenance (4 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69fcf1b3d9a08190850b388308656266 |
completed | May 7, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69fcf0226d8c8190b23dceafb1794995 |
completed | May 7, 2026, 8:03 p.m. |
| PDg | Predicate description generation | batch_69fcf1b241888190a243f07051c71383 |
completed | May 7, 2026, 8:10 p.m. |
Created at: April 28, 2026, 5:46 a.m.