Triple
T32654918
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alan Rufus |
E834834
|
entity |
| Predicate | mainEnglishPowerBase |
P174769
|
FINISHED |
| Object | Richmondshire |
—
|
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: Richmondshire | Statement: [Alan Rufus, mainEnglishPowerBase, Richmondshire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainEnglishPowerBase Context triple: [Alan Rufus, mainEnglishPowerBase, Richmondshire]
-
A.
englishPart
Indicates that one entity is a component, segment, or subset of another within the context of English (e.g., English text, language, or content).
-
B.
principalEnglishLanguageOrganOf
Indicates that one entity serves as the main official body responsible for the use, regulation, or promotion of the English language for another entity.
-
C.
EnglishStrength
Indicates the degree or level of proficiency or capability in using the English language.
-
D.
EnglishTactic
Indicates a tactical or strategic action carried out using the English language as the primary medium or method.
-
E.
EnglishCommander
Indicates that one entity serves as a military commander or leader for English forces in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69f3492f72248190ba42fa596aea50e1 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6c7e32ec08190b74856937c4a9fc3 |
completed | May 3, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f617c08190a70ba880210f908c |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c77500a08190b2bdeca33bd2ac08 |
completed | May 3, 2026, 3:56 a.m. |
Created at: May 1, 2026, 1:08 a.m.