Triple
T37173470
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate monument controversy |
E920976
|
entity |
| Predicate | mainlyConcerns |
P106402
|
FINISHED |
| Object | Confederate monuments |
—
|
NE NERFINISHED |
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: Confederate monuments | Statement: [Confederate monument controversy, mainlyConcerns, Confederate monuments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainlyConcerns Context triple: [Confederate monument controversy, mainlyConcerns, Confederate monuments]
-
A.
subjectOfConcernFor
Indicates that one entity is regarded as a matter of worry, interest, or attention for another entity.
-
B.
concernsAddressed
Indicates that specific issues, worries, or topics raised by one party have been acknowledged and dealt with by another party.
-
C.
concernsDomain
chosen
Indicates that something (such as an action, statement, or item) is about, relates to, or is focused on a particular domain or field.
-
D.
concernsTitle
Indicates that something is about or relates specifically to a particular title (such as a name, designation, or formal heading).
-
E.
concernsRight
Indicates that something is about or relates specifically to a legal or moral right held by an entity.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb55de3b9c8190a7656aeab3c3ffbc |
completed | May 6, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69fb35bc92e08190bff447624e2df791 |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:15 p.m.