Triple
T10904031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brighton i360 |
E257520
|
entity |
| Predicate | podMovement |
P70961
|
FINISHED |
| Object | slides up and down the tower |
—
|
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: slides up and down the tower | Statement: [Brighton i360, podMovement, slides up and down the tower]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: podMovement Context triple: [Brighton i360, podMovement, slides up and down the tower]
-
A.
movementIn
Indicates a relationship where an entity moves within, into, or inside a specified area, space, or container.
-
B.
movementFor
Indicates that one entity moves on behalf of, in support of, or as a representative action for another entity.
-
C.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
-
D.
describesMovement
chosen
Indicates that an entity undergoes or performs a change of position or location, capturing how it moves from one place or state to another.
-
E.
usesMovement
Indicates that an entity performs or involves some form of movement as part of its action or behavior.
- 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_69d6aa8550c8819095508a2ed9acf3db |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d761a5dffc8190927b0928978646a4 |
completed | April 9, 2026, 8:21 a.m. |
| PD | Predicate disambiguation | batch_69d70d3d69e08190bb369e9a7927142c |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:22 p.m.