Triple
T14741672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gold Coaster |
E346362
|
entity |
| Predicate | hasInversionType |
P63750
|
FINISHED |
| Object | vertical loop |
—
|
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: vertical loop | Statement: [The Gold Coaster, hasInversionType, vertical loop]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInversionType Context triple: [The Gold Coaster, hasInversionType, vertical loop]
-
A.
hasInversionCapability
Indicates that an entity possesses the ability to reverse or invert another entity, state, or process.
-
B.
hasInversionCount
Indicates that there is a specific number of pairwise order inversions present in a given sequence or arrangement.
-
C.
inversionType
chosen
Indicates the specific kind or category of inversion relationship that holds between entities, such as one being the reverse, opposite, or role-swapped form of the other.
-
D.
isInverseOf
Indicates that one relation reverses the direction of another, so that if the original relates A to B, its inverse relates B to A.
-
E.
hasTransformationType
Indicates that an entity undergoes or is associated with a specific kind or category of transformation.
- 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_69d822e6f1c88190bc494d491a907114 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69dec7367a1c819081082cc355e385fa |
completed | April 14, 2026, 11:01 p.m. |
| PD | Predicate disambiguation | batch_69de8bf9331481909582045cd567d91f |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:30 a.m.