Triple
T354006
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Democratic-Republican Party |
E7504
|
entity |
| Predicate | coreSupportBase |
P4178
|
FINISHED |
| Object | Southern planters |
—
|
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: Southern planters | Statement: [Democratic-Republican Party, coreSupportBase, Southern planters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSupportBase Context triple: [Democratic-Republican Party, coreSupportBase, Southern planters]
-
A.
supportBase
chosen
Indicates that one entity serves as a foundational or backing structure that physically or functionally supports another entity.
-
B.
mainBase
Indicates that one entity serves as the primary or central base or headquarters for another entity.
-
C.
coreCommand
Indicates that one entity serves as the primary or central command or control authority over another entity or process.
-
D.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
E.
supportsFeature
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
- 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_69a2e7e696948190bebc966535995e45 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb80f524819093f4c2c18c3d615f |
completed | Feb. 28, 2026, 1:20 p.m. |
| PD | Predicate disambiguation | batch_69a2e9571bd88190b6fcb16f21604720 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.