Triple
T20157929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Line 7 |
E491623
|
entity |
| Predicate | isPartOfUrbanTransitSystem |
P8428
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Line 7, isPartOfUrbanTransitSystem, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPartOfUrbanTransitSystem Context triple: [Line 7, isPartOfUrbanTransitSystem, true]
-
A.
partOfTransitSystem
chosen
Indicates that something is a component or segment within a larger transit or transportation system.
-
B.
hasFormOfPublicTransit
Indicates that one entity provides or is associated with a particular type or mode of public transportation for another entity or context.
-
C.
appliesToTransitSystem
Indicates that something (such as a rule, policy, feature, or condition) is relevant or applicable to a particular transit or transportation system.
-
D.
usedByTransitSystem
Indicates that something is utilized or operated by a transit or public transportation system.
-
E.
isPublicTransport
Indicates that the entity functions as a mode or instance of transportation that is available for use by the general public, typically operating on fixed routes or schedules.
- 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_69da6265f8f0819080b29c752a574088 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e667e18a0c8190a2cc2b305da28047 |
completed | April 20, 2026, 5:52 p.m. |
| PD | Predicate disambiguation | batch_69e54cfd924881909b55f3e4d3e7e070 |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 11:34 p.m.