Triple
T33608459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meridian Campaign |
E860921
|
entity |
| Predicate | secondaryTargetArea |
P26823
|
FINISHED |
| Object | central Mississippi |
—
|
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: central Mississippi | Statement: [Meridian Campaign, secondaryTargetArea, central Mississippi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondaryTargetArea Context triple: [Meridian Campaign, secondaryTargetArea, central Mississippi]
-
A.
secondaryTarget
Indicates that an entity serves as an additional or subordinate target in relation to a primary target within a given context or action.
-
B.
targetArea
Indicates the specific area or region that is the intended focus or destination of an action or effect.
-
C.
secondaryGeographicFocus
chosen
Indicates a secondary or less primary geographic area that is also a focus or target of the entity’s activities, influence, or relevance.
-
D.
secondaryTo
Indicates that one condition, event, or factor occurs as a consequence of, or is caused by, another primary condition, event, or factor.
-
E.
secondaryAreaOfUse
Indicates that an entity has an additional, non-primary context, domain, or purpose in which it is used.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fedfd913f48190bdcd450980868d9a |
completed | May 9, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fedf58c6e88190821a7156054c9086 |
completed | May 9, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:41 a.m.