Triple
T9430663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TH 26 |
E227364
|
entity |
| Predicate | workOrchestration |
P67492
|
FINISHED |
| Object | orchestra |
—
|
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: orchestra | Statement: [TH 26, workOrchestration, orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workOrchestration Context triple: [TH 26, workOrchestration, orchestra]
-
A.
helpsOrchestrate
chosen
Indicates involvement in coordinating, organizing, or managing the execution of an activity or process, often in collaboration with others.
-
B.
workDirector
Indicates that one entity serves as the director (creative or managerial lead) of a particular work or production associated with the other entity.
-
C.
workDistributor
Indicates that one entity is responsible for assigning, allocating, or distributing work or tasks to others.
-
D.
worksStatus
Indicates the current state or condition of an entity’s work or project, such as whether it is planned, in progress, completed, or otherwise categorized.
-
E.
coordinatesWorkOf
Indicates overseeing and organizing the tasks, efforts, or activities of others to ensure they work together effectively toward a common goal.
- 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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7e5ed7408190beda5fb078e9345a |
completed | April 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69cca55548488190b171ae695a3212de |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.