Triple
T25997612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Municipal Subway 10 series |
E646527
|
entity |
| Predicate | hasPassengerDoorsOn |
P128223
|
FINISHED |
| Object | both sides |
—
|
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: both sides | Statement: [Osaka Municipal Subway 10 series, hasPassengerDoorsOn, both sides]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPassengerDoorsOn Context triple: [Osaka Municipal Subway 10 series, hasPassengerDoorsOn, both sides]
-
A.
hasDoors
Indicates that an object or structure possesses one or more doors.
-
B.
vehicleDoorType
chosen
Indicates the specific style or configuration of doors that a vehicle has.
-
C.
numberOfDoors
Indicates the quantity of doors associated with an entity.
-
D.
hasDoorsOperation
Indicates that an entity has a specific type or mode of operation for its doors (e.g., how they open, close, or are controlled).
-
E.
hasDoor
Indicates that one entity possesses or is equipped with a door that provides access to or through it.
- 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_69e77e88cb8481908da31d4a00661f55 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 22, 2026, 8:58 a.m.