Triple
T10783634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New World Symphony |
E254392
|
entity |
| Predicate | trainingField |
P2424
|
FINISHED |
| Object | orchestral performance |
—
|
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: orchestral performance | Statement: [New World Symphony, trainingField, orchestral performance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trainingField Context triple: [New World Symphony, trainingField, orchestral performance]
-
A.
trainingGround
chosen
Indicates a location or context where entities engage in practice, drills, or preparation activities to develop or improve skills.
-
B.
trainingGroundFor
Indicates that one entity serves as a place or context where another entity is trained, prepared, or developed.
-
C.
training
Indicates that one entity is teaching, coaching, or otherwise helping another entity acquire or improve a skill, behavior, or capability.
-
D.
trainingComponent
Indicates that one entity functions as a training-related part, module, or element within a larger training process or system involving another entity.
-
E.
trainingSystem
Indicates a system or framework used to train, instruct, or develop skills or knowledge in a target entity.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732d1b4bc8190871dd21265065705 |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.