Triple
T22920209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atlantica SuperSplash |
E568838
|
entity |
| Predicate | hasBackwardDrop |
P57946
|
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: [Atlantica SuperSplash, hasBackwardDrop, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackwardDrop Context triple: [Atlantica SuperSplash, hasBackwardDrop, true]
-
A.
hasFinalDrop
Indicates that an entity experiences or possesses a last or concluding decrease, reduction, or decline in some quantity, state, or value.
-
B.
hasBackTo
Indicates that one entity is positioned or oriented with its back facing toward another entity.
-
C.
hasBackwardsSection
Indicates that an entity contains a segment or portion that is oriented, ordered, or directed in the reverse of the primary or expected direction.
-
D.
canBePulledBackAlong
Indicates that a structure or object can be transferred or redefined along a given mapping or morphism so that it is compatible with that mapping.
-
E.
hasDropType
chosen
Indicates that an entity is associated with a specific type or category of drop (e.g., item, reward, or resource obtained).
- 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_69e2458d90c88190a58cead4e781ca6a |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f180d40f98819096210c097b47d43b |
completed | April 29, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69ef3b7c5fc081909ac50c5c8569cc19 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:42 p.m.