Triple
T31755036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang roller coaster model |
E810534
|
entity |
| Predicate | numberOfInversionsPerCycle |
P78083
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Boomerang roller coaster model, numberOfInversionsPerCycle, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfInversionsPerCycle Context triple: [Boomerang roller coaster model, numberOfInversionsPerCycle, 3]
-
A.
inversionsTakenForwardsAndBackwards
Indicates that the number or pattern of inversions is considered or measured in both the forward and reverse directions of a sequence or structure.
-
B.
opusNumberOfCycle
Indicates that a specific opus number identifies or is assigned to a particular musical cycle.
-
C.
hasInversionCount
chosen
Indicates that there is a specific number of pairwise order inversions present in a given sequence or arrangement.
-
D.
hasNumberInCycle
Indicates that a given number appears within a specified repeating sequence or cycle associated with an entity or process.
-
E.
inversions
Indicates a relationship where the usual order, position, or hierarchy between elements is reversed or turned upside down.
- 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_69f348e340d48190b780fae618c51464 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a013e23698c81909a32d371b6f158d0 |
completed | May 11, 2026, 2:25 a.m. |
| PD | Predicate disambiguation | batch_6a013db04b108190985897aa6e95b4ec |
completed | May 11, 2026, 2:23 a.m. |
Created at: April 30, 2026, 11:29 p.m.