Triple
T26777480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lord of Friesland |
E670154
|
entity |
| Predicate | hasAbolishedBy |
P96088
|
FINISHED |
| Object | emergence of the Dutch Republic |
—
|
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: emergence of the Dutch Republic | Statement: [Lord of Friesland, hasAbolishedBy, emergence of the Dutch Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbolishedBy Context triple: [Lord of Friesland, hasAbolishedBy, emergence of the Dutch Republic]
-
A.
isAbolished
Indicates that a law, practice, institution, or entity has been formally ended and is no longer in legal or official effect.
-
B.
wasAbolishedBy
chosen
Indicates that an institution, practice, law, or entity ceased to exist or operate as a result of an action taken by another entity.
-
C.
abolishedAfter
Indicates that one entity was abolished at a later time than another entity was abolished.
-
D.
canBeAbolishedBy
Indicates that one entity has the authority or power to formally end, revoke, or eliminate another entity.
-
E.
abolishedAsState
Indicates that a political entity or territorial unit ceased to exist in its former status as a state due to formal abolition.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f619778a588190a1d2375eff7a628f |
completed | May 2, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69f60b8dfa0c8190864e1a940024d0a0 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 4:06 a.m.