Triple
T5305333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Carolina on My Mind |
E120086
|
entity |
| Predicate | isPerformedAt |
P270
|
FINISHED |
| Object | state events in South Carolina |
—
|
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: state events in South Carolina | Statement: [South Carolina on My Mind, isPerformedAt, state events in South Carolina]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPerformedAt Context triple: [South Carolina on My Mind, isPerformedAt, state events in South Carolina]
-
A.
performsAt
chosen
Indicates that an entity carries out or presents a performance at a specific location, venue, or event.
-
B.
performedTo
Indicates that an action or performance is directed toward or carried out on a particular entity.
-
C.
performedWith
Indicates that an action or activity is carried out using, accompanied by, or in conjunction with a specified entity or instrument.
-
D.
executedDuring
Indicates that an action or event was carried out within the temporal span of another specified event or period.
-
E.
firstPerformedOn
Indicates the date or occasion on which an action, event, or performance was carried out for the first time on a particular subject or object.
- 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_69bd44704be88190acdb2ac481b0ff55 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd86f20f008190be7b5848af05f2b8 |
completed | March 20, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69bd84534f9c8190bc19d4812060768d |
completed | March 20, 2026, 5:30 p.m. |
Created at: March 20, 2026, 1:53 p.m.