Triple
T7160026
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midlothian campaign |
E166917
|
entity |
| Predicate | hasAnalysisIn |
P62814
|
FINISHED |
| Object | historiography of British politics |
—
|
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: historiography of British politics | Statement: [Midlothian campaign, hasAnalysisIn, historiography of British politics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAnalysisIn Context triple: [Midlothian campaign, hasAnalysisIn, historiography of British politics]
-
A.
hasAnalysis
chosen
Indicates that an entity is associated with, or has undergone, a particular analysis or examination.
-
B.
analyzes
Indicates that one entity systematically examines or evaluates another entity to understand its nature, structure, or components.
-
C.
helpsAnalyze
Indicates that one entity assists another in examining, interpreting, or understanding something in a more detailed or effective way.
-
D.
hasRegressionAnalysis
Indicates that a regression analysis has been performed on, or is associated with, a given dataset, model, or relationship between variables.
-
E.
hasANC
Indicates that an entity has received or is associated with antenatal care (ANC) services.
- 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_69c68887a5cc8190bec0ea96227164f7 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e811d6b081909dafeee1d820c74f |
completed | March 27, 2026, 8:26 p.m. |
| PD | Predicate disambiguation | batch_69c6e1cd5c948190a9113b23f7308c21 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:47 p.m.