Triple
T24472409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tinikling |
E617136
|
entity |
| Predicate | poleMovementPattern |
P14493
|
FINISHED |
| Object | clapping together and apart |
—
|
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: clapping together and apart | Statement: [Tinikling, poleMovementPattern, clapping together and apart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poleMovementPattern Context triple: [Tinikling, poleMovementPattern, clapping together and apart]
-
A.
movementType
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
B.
describesMovement
Indicates that an entity undergoes or performs a change of position or location, capturing how it moves from one place or state to another.
-
C.
typicalMovement
Indicates the usual or characteristic way in which an entity moves or is expected to move.
-
D.
movementAcross
Indicates movement of an entity from one side or area to another, traversing through or over an intervening space or boundary.
-
E.
movementCharacteristic
chosen
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f29944bea081908f8a732495d67cfc |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
Created at: April 18, 2026, 2:20 a.m.