Triple
T17814818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Republican Party |
E444808
|
entity |
| Predicate | coreSupportGroup |
P16415
|
FINISHED |
| Object | commercial interests |
—
|
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: commercial interests | Statement: [National Republican Party, coreSupportGroup, commercial interests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coreSupportGroup Context triple: [National Republican Party, coreSupportGroup, commercial interests]
-
A.
coreTeam
Indicates that an entity is a primary, central member of a core group responsible for key decisions or activities within an organization or project.
-
B.
mainSupportBase
Indicates that one entity serves as the primary structural or functional support base for another entity.
-
C.
providesSupportTo
chosen
Indicates that one entity offers help, resources, or reinforcement to another entity to aid its function, stability, or success.
-
D.
controlGroup
Indicates that one entity functions as the control group against which another condition, treatment, or experimental group is compared.
-
E.
coreModule
Indicates that something functions as a primary or foundational module within a larger system or structure.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887e80688190a2ac3308b0e815c6 |
completed | April 19, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:14 a.m.