Triple
T25833166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manora dance |
E650719
|
entity |
| Predicate | performedForPurpose |
P98
|
FINISHED |
| Object | entertainment |
—
|
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: entertainment | Statement: [Manora dance, performedForPurpose, entertainment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedForPurpose Context triple: [Manora dance, performedForPurpose, entertainment]
-
A.
governedForPurpose
Indicates that one entity exercises governance or control over another specifically to achieve a particular purpose or intended function.
-
B.
programmedPurpose
Indicates that an entity has been intentionally designed or configured to fulfill a specific function, goal, or behavior.
-
C.
hasEstablishedPurpose
Indicates that an entity has a defined and recognized purpose or intended function already determined.
-
D.
operationalPurpose
Indicates the function, role, or intended use that an entity is designed or configured to perform in an operational context.
-
E.
usedFor
chosen
Indicates that one entity serves a purpose, function, or role in accomplishing, enabling, or supporting another entity or activity.
- 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_69e7ab37438081908f1ccf6284839520 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c1f94ac8190bc6fbc7916fc0d82 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 22, 2026, 7:39 a.m.