Triple
T5079305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Coaster |
E114475
|
entity |
| Predicate | hasInversionCapability |
P61296
|
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: [Flying Coaster, hasInversionCapability, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInversionCapability Context triple: [Flying Coaster, hasInversionCapability, yes]
-
A.
isCapableOf
Indicates that an entity has the ability or capacity to perform a particular action or function.
-
B.
tiltingCapability
Indicates the ability of one entity to tilt or be tilted relative to another or to a reference orientation.
-
C.
supportsBidirectionalPower
Indicates that an entity can both supply and receive power, allowing electrical energy to flow in either direction between connected systems.
-
D.
capabilityType
Indicates the type or category of capability that an entity possesses or is associated with.
-
E.
couplingCapability
Indicates the ability or suitability of one entity to connect, link, or interface with another in a functional or compatible manner.
- F. None of above. chosen
Provenance (4 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74f75cf0819088be9e076eaf3168 |
completed | March 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
| PDg | Predicate description generation | batch_69bd73d90b608190bd6c2407e84e2b64 |
completed | March 20, 2026, 4:20 p.m. |
Created at: March 20, 2026, 1:39 p.m.