Triple
T7391151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | History of England |
E170498
|
entity |
| Predicate | typeOfHistory |
P66217
|
FINISHED |
| Object | national history |
—
|
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: national history | Statement: [History of England, typeOfHistory, national history]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfHistory Context triple: [History of England, typeOfHistory, national history]
-
A.
historicalType
chosen
Indicates that one entity classifies or characterizes another in terms of its role, status, or category within a historical context.
-
B.
hasTypeHistory
Indicates that an entity is associated with a record or sequence of its past and present types or classifications over time.
-
C.
classHistory
Indicates a relationship where an entity records or reflects the historical versions, changes, or evolution of a particular class over time.
-
D.
historicalStatusOf
Indicates the historical condition, role, or classification that an entity held during a specific past period or context.
-
E.
historicalMigrationType
Indicates the type or category of migration that occurred in a historical context between entities.
- 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_69c68a5e2c9081909e713ce866e0060a |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f22318108190a4dde257fe9e947f |
completed | March 27, 2026, 9:09 p.m. |
| PD | Predicate disambiguation | batch_69c6f0309cc88190b55d278969400294 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:09 p.m.