Triple
T11608745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Udakkiya |
E275326
|
entity |
| Predicate | ensembleRole |
P40371
|
FINISHED |
| Object | time-keeping instrument in ritual ensembles |
—
|
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: time-keeping instrument in ritual ensembles | Statement: [Udakkiya, ensembleRole, time-keeping instrument in ritual ensembles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ensembleRole Context triple: [Udakkiya, ensembleRole, time-keeping instrument in ritual ensembles]
-
A.
encodingRole
Indicates the role or function an entity has in the process of encoding information into a particular form or representation.
-
B.
sonRole
Indicates that one entity holds the role or relationship of a son with respect to another entity.
-
C.
unitRole
chosen
Indicates the functional role or purpose that a unit serves within a larger system or context.
-
D.
allianceRole
Indicates the specific function, status, or responsibility an entity holds within an alliance or cooperative partnership.
-
E.
hasEnsembleRoleWith
Indicates that two or more entities share a collaborative or joint role within the same ensemble, group, or collective context.
- 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_69d6aaf84b548190ac072e4fb89ae18f |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a04231d08190b8a07cd977d11ffa |
completed | April 10, 2026, 7:01 a.m. |
| PD | Predicate disambiguation | batch_69d85dd20d188190863d1190d4c16048 |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.