Triple
T24274097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gore family |
E605358
|
entity |
| Predicate | hasNationalInfluence |
P75457
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Gore family, hasNationalInfluence, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNationalInfluence Context triple: [Gore family, hasNationalInfluence, yes]
-
A.
hasRegionalInfluenceFrom
Indicates that one entity’s influence, impact, or authority in a region is derived from or shaped by another entity.
-
B.
hasSignificantInfluenceIn
Indicates that one entity exerts a substantial impact or shaping effect on another entity within a particular domain, context, or outcome.
-
C.
countryInfluence
Indicates the degree to which one country affects or shapes the policies, decisions, or conditions within another country or in the international arena.
-
D.
hasExternalInfluence
Indicates that one entity affects or alters another entity due to factors or forces originating outside the affected entity.
-
E.
hasInfluenceScope
chosen
Indicates the range or extent within which an entity’s influence, impact, or authority is effective or applicable.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28d5da53c8190810f4e7777d112ba |
completed | April 29, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:07 a.m.