Triple
T250557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tinikling |
E5136
|
entity |
| Predicate | typicalFormation |
P8574
|
FINISHED |
| Object | two bamboo pole handlers and two dancers |
—
|
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: two bamboo pole handlers and two dancers | Statement: [tinikling, typicalFormation, two bamboo pole handlers and two dancers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalFormation Context triple: [tinikling, typicalFormation, two bamboo pole handlers and two dancers]
-
A.
typicalTeamDesignation
Indicates the standard or commonly used team name or label that is typically assigned to an entity.
-
B.
typicalNotation
Indicates that one entity is the standard or commonly used symbolic representation (notation) for another entity.
-
C.
typicalTeamSize
Indicates the usual or most common number of members that make up a given team.
-
D.
typicalMembers
Indicates that the related entities are representative or characteristic members of a larger group, category, or class.
-
E.
shaped
Indicates that one entity has given form, contour, or structure to another entity or outcome.
- F. None of above. chosen
Provenance (4 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_69a257c4bf688190a46ebbf411ab7473 |
completed | Feb. 28, 2026, 2:49 a.m. |
| NER | Named-entity recognition | batch_69a25d38aba8819081d0958eb60ce27e |
completed | Feb. 28, 2026, 3:12 a.m. |
| PD | Predicate disambiguation | batch_69a25b665f8c8190aac6fcbba2a0eebb |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c036b54819090a101c4cbdbcff7 |
completed | Feb. 28, 2026, 3:07 a.m. |
Created at: Feb. 28, 2026, 2:54 a.m.