Triple
T35581400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Class 4000 DMU |
E1028231
|
entity |
| Predicate | hasAccessibleArea |
P64475
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Class 4000 DMU, hasAccessibleArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAccessibleArea Context triple: [Class 4000 DMU, hasAccessibleArea, yes]
-
A.
hasAccessibleAccess
Indicates that an entity provides a form of access that is usable and reachable under defined accessibility conditions or standards.
-
B.
isAccessible
Indicates that one entity can be reached, used, or entered by another entity without obstruction or restriction.
-
C.
hasDisplayArea
Indicates that an entity includes or is associated with a specific physical or virtual area used for displaying content or items.
-
D.
areAccessibleAt
Indicates that certain entities can be reached, used, or entered at a specified location, time, or context.
-
E.
hasWorkArea
chosen
Indicates that one entity possesses, is assigned, or is associated with a specific physical or conceptual work area.
- 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_69f76e0495a081909beced418558c0b4 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fcc7338120819081cb46547d60f2cb |
completed | May 7, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_69fcc58566a0819082d5ea36e03bf0c6 |
completed | May 7, 2026, 5:01 p.m. |
Created at: May 3, 2026, 4:04 p.m.