Triple
T8697206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Carolina State House |
E206430
|
entity |
| Predicate | hasEvidenceOfEvent |
P70490
|
FINISHED |
| Object | bronze stars marking Union artillery hits |
—
|
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: bronze stars marking Union artillery hits | Statement: [South Carolina State House, hasEvidenceOfEvent, bronze stars marking Union artillery hits]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEvidenceOfEvent Context triple: [South Carolina State House, hasEvidenceOfEvent, bronze stars marking Union artillery hits]
-
A.
hasMaterialEvidence
chosen
Indicates that there exists tangible, physical evidence supporting or associated with a particular entity, event, or claim.
-
B.
hadEvent
Indicates that an entity experienced, hosted, or was associated with a specific event at some point in time.
-
C.
hasEvidentials
Indicates that a statement, claim, or information is accompanied by markers specifying the type or source of evidence supporting it.
-
D.
providesEvidenceFor
Indicates that one entity serves as support, justification, or proof for the validity or truth of another entity.
-
E.
hasNoEvidenceOf
Indicates that there is no supporting proof, data, or documentation confirming the existence or occurrence of the referenced condition, event, or relationship.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.