Triple
T2857959
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flint Symphony Orchestra |
E63247
|
entity |
| Predicate | hasPerformanceFormat |
P38824
|
FINISHED |
| Object | subscription concerts |
—
|
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: subscription concerts | Statement: [Flint Symphony Orchestra, hasPerformanceFormat, subscription concerts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPerformanceFormat Context triple: [Flint Symphony Orchestra, hasPerformanceFormat, subscription concerts]
-
A.
hasPerformanceConvention
Indicates that there is an agreed-upon set of rules, norms, or standards governing how a particular performance or activity should be carried out.
-
B.
hasProductionFormat
Indicates that an entity is associated with, or presented in, a particular production or media format.
-
C.
operatesInFormat
chosen
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
D.
hasExhibitFormat
Indicates the specific format or medium in which an exhibit is presented or made available.
-
E.
originalPerformanceFor
Indicates that one entity is the original performance or execution from which another related version, recording, or representation is derived.
- 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_69ab4c41e8c08190a9e8f5249cc12610 |
completed | March 6, 2026, 9:50 p.m. |
| NER | Named-entity recognition | batch_69abdf89d3b4819086936f26d8683a2a |
completed | March 7, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69abdd10aef88190b750aae07e7df4dc |
completed | March 7, 2026, 8:08 a.m. |
Created at: March 6, 2026, 10:02 p.m.