Triple
T5921096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Estimated Prophet |
E131700
|
entity |
| Predicate | livePerformanceFrequency |
P3288
|
FINISHED |
| Object | frequently performed in concert |
—
|
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: frequently performed in concert | Statement: [Estimated Prophet, livePerformanceFrequency, frequently performed in concert]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: livePerformanceFrequency Context triple: [Estimated Prophet, livePerformanceFrequency, frequently performed in concert]
-
A.
performedFrequency
Indicates how often an action or activity is carried out within a given time period.
-
B.
frequentPerformance
Indicates that an entity regularly or repeatedly carries out a particular performance or activity over a period of time.
-
C.
livePerformanceFeature
Indicates that one entity is included or highlighted as a component of another entity’s live performance.
-
D.
livePerformanceStapleFor
chosen
Indicates that something (such as a song or piece) is regularly and prominently featured in another entity’s live performances.
-
E.
frequentlyPerformedAt
Indicates that an action or event occurs regularly or with high frequency at a particular location or 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_69c0085a1ed08190a7e9a8b6323fd680 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
Created at: March 22, 2026, 4 p.m.