Triple
T34293190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Low Countries |
E879947
|
entity |
| Predicate | historicalTermUsedIn |
P152886
|
FINISHED |
| Object | Dutch historiography |
—
|
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: Dutch historiography | Statement: [Northern Low Countries, historicalTermUsedIn, Dutch historiography]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalTermUsedIn Context triple: [Northern Low Countries, historicalTermUsedIn, Dutch historiography]
-
A.
historicalTermFor
chosen
Indicates that one term was historically used to refer to, describe, or name the other entity in an earlier time or context.
-
B.
historicalNameUsedIn
Indicates that a historical or former name was used to refer to a particular entity in some context.
-
C.
historicalExpression
Indicates that something serves as an expression, representation, or manifestation of a historical period, event, or context.
-
D.
historicalPeriodOfNotableUse
Indicates the historical time period during which the entity was notably or most prominently used.
-
E.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
- 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_69f349b6df1c81908e5e5b6c2ab6409b |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00532815c881908f10d9594458b3d7 |
completed | May 10, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_6a0052b9f030819081b8105bdcaf6d8f |
completed | May 10, 2026, 9:41 a.m. |
Created at: May 1, 2026, 1:57 a.m.