Triple
T4383270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American Folk Festival (historical host) |
E99179
|
entity |
| Predicate | bringsPerformersFrom |
P56504
|
FINISHED |
| Object | across the United States |
—
|
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: across the United States | Statement: [American Folk Festival (historical host), bringsPerformersFrom, across the United States]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bringsPerformersFrom Context triple: [American Folk Festival (historical host), bringsPerformersFrom, across the United States]
-
A.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
B.
coPerformer
Indicates that two or more entities jointly perform the same act or participate together in the same performance.
-
C.
associatedWithPerformer
Indicates a relationship in which something (such as a work, event, or role) is connected or linked to a specific performer.
-
D.
performedBy
Indicates that an action, task, or event is carried out or executed by a specified agent or entity.
-
E.
presentsPerformancesBy
Indicates that one entity organizes or stages performances that feature or are carried out by another entity.
- F. None of above. chosen
Provenance (4 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35262649c8190a724c9835cb7ece6 |
completed | March 12, 2026, 11:55 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b35034cd248190bae09e9d090e13ec |
completed | March 12, 2026, 11:45 p.m. |
Created at: March 12, 2026, 11:18 p.m.