Triple
T21731448
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Custom Looping Coaster |
E536413
|
entity |
| Predicate | loopingElements |
P24449
|
FINISHED |
| Object | are specifically engineered for each project |
—
|
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: are specifically engineered for each project | Statement: [Custom Looping Coaster, loopingElements, are specifically engineered for each project]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: loopingElements Context triple: [Custom Looping Coaster, loopingElements, are specifically engineered for each project]
-
A.
formsLoopWith
Indicates that two or more entities are connected in such a way that they form a closed cycle or loop with one another.
-
B.
loopsFrom
Indicates that a path, process, or connection starts at a given point and returns back to that same point, forming a loop.
-
C.
loopType
chosen
Indicates the specific kind or category of loop structure or iteration pattern used in a process or control flow.
-
D.
isLoop
Indicates that something forms or behaves as a closed, repeating cycle or path that returns to its starting point.
-
E.
loopsTo
Indicates that an entity has a path or connection that starts and ends at the same point, forming a loop back to itself.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69effd0713c48190a38b3963cb3cbaf0 |
completed | April 28, 2026, 12:19 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.