Triple
T17149287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Lantern (Six Flags Great Adventure) |
E416175
|
entity |
| Predicate | hasVerticalLoop |
P98787
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Green Lantern (Six Flags Great Adventure), hasVerticalLoop, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVerticalLoop Context triple: [Green Lantern (Six Flags Great Adventure), hasVerticalLoop, true]
-
A.
hasVerticalLoops
chosen
Indicates that one entity features or includes vertical loop structures in its form, design, or configuration.
-
B.
hasLoopRole
Indicates that an entity participates in a loop structure with a specific functional role within that loop.
-
C.
hasLoopConfiguration
Indicates that an entity is associated with a specific loop setup or arrangement that defines how a loop operates or is structured.
-
D.
hasPassingLoopAt
Indicates that a railway line or track segment includes a passing loop located at a specified place or point.
-
E.
hasLoopMode
Indicates that an entity operates or is configured in a mode where its behavior or process repeats in a loop.
- 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_69d886d279c081909f8ff1f743ddeb69 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f4059d90819092d3609326fa3130 |
completed | April 18, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.