Triple
T6514832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adenoid Hynkel |
E148228
|
entity |
| Predicate | basedOnHistoricalPeriod |
P41036
|
FINISHED |
| Object | World War II era |
—
|
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: World War II era | Statement: [Adenoid Hynkel, basedOnHistoricalPeriod, World War II era]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnHistoricalPeriod Context triple: [Adenoid Hynkel, basedOnHistoricalPeriod, World War II era]
-
A.
historicallyBasedOn
Indicates that something is derived from, inspired by, or modeled on historical events, sources, or precedents.
-
B.
historicalPeriodOfSignificance
Indicates the time period during which an entity is considered to have had its most important or influential historical impact.
-
C.
historicalPeriodOfUse
Indicates the time period during which something was in active use or commonly utilized.
-
D.
locatedInHistoricPeriod
chosen
Indicates that an entity exists, occurs, or is situated within a specific historic period or era.
-
E.
historicallyConsidered
Indicates that one entity has been regarded or classified in a particular way relative to another entity during a past historical period.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ac0bea808190aebc2905fb53eeba |
completed | March 27, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69c68ab98c78819081743e614df04e1d |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:44 p.m.