Triple
T25069672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Count Egmont |
E627873
|
entity |
| Predicate | inspiredByHistoricalEvent |
P2107
|
FINISHED |
| Object | Eighty Years' War |
—
|
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: Eighty Years' War | Statement: [Count Egmont, inspiredByHistoricalEvent, Eighty Years' War]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredByHistoricalEvent Context triple: [Count Egmont, inspiredByHistoricalEvent, Eighty Years' War]
-
A.
hasHistoricalEvent
chosen
Indicates that a historical event occurred in, is associated with, or is relevant to a particular entity.
-
B.
historicalEventDescribedAs
Indicates that a historical event is characterized or portrayed using a particular description, label, or narrative.
-
C.
historicalEventsDescribed
Indicates that one entity (such as a document, text, or account) describes or recounts the historical events associated with another entity.
-
D.
hasHistoricSignificanceFor
Indicates that something holds notable historical importance or relevance for a particular entity or group.
-
E.
basedOnHistoricalFigure
Indicates that something is derived from, inspired by, or modeled after a real historical person.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 6:10 a.m.