Triple
T35319358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JR West 283 series |
E1019992
|
entity |
| Predicate | hasTiltingCapability |
P23580
|
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: [JR West 283 series, hasTiltingCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTiltingCapability Context triple: [JR West 283 series, hasTiltingCapability, yes]
-
A.
tiltingCapability
chosen
Indicates the ability of one entity to tilt or be tilted relative to another or to a reference orientation.
-
B.
tiltingMechanism
Indicates a relationship where one entity serves as a mechanism that enables another entity to tilt or be tilted.
-
C.
hasRotationCharacteristic
Indicates that one entity possesses a specific rotational property, behavior, or attribute in relation to another entity or reference frame.
-
D.
hasRotationMechanic
Indicates that the subject includes or supports a gameplay or functional mechanic involving rotation or turning as a core interaction.
-
E.
gimbalCapability
Indicates the ability of a system or device to support and control a gimbal’s movement or stabilization functions.
- 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_69f76de9d45c81908a2ed0956b448b65 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: May 3, 2026, 4:03 p.m.