Triple
T20314645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE TD |
E510346
|
entity |
| Predicate | hasTiltingTechnology |
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: [ICE TD, hasTiltingTechnology, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTiltingTechnology Context triple: [ICE TD, hasTiltingTechnology, 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.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
D.
hasSlidingMechanism
Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
-
E.
tiltedRelativeTo
Indicates that one entity is oriented at an angle with respect to another, rather than being parallel or perpendicular.
- 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_69e0b4c7491c8190961113c4283b10b0 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e67786f4dc8190b02a6c2a4338362d |
completed | April 20, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69e55b21b09081909e46691b6f45a07f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 16, 2026, 11:19 a.m.