Triple
T24174217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaanse Rijk |
E599229
|
entity |
| Predicate | hoogtepuntMacht |
P155582
|
FINISHED |
| Object | 16e eeuw |
—
|
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: 16e eeuw | Statement: [Spaanse Rijk, hoogtepuntMacht, 16e eeuw]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hoogtepuntMacht Context triple: [Spaanse Rijk, hoogtepuntMacht, 16e eeuw]
-
A.
highestPoint
Indicates that one entity is the point with the greatest elevation or height relative to another entity or defined area.
-
B.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
C.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
-
D.
highPointLocatedOn
Indicates that the highest point of one entity is situated on or atop another entity.
-
E.
powersAscentOf
Indicates that one entity provides the driving force, energy, or enabling influence behind another entity’s rise, advancement, or upward progression.
- F. None of above. chosen
Provenance (4 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_69e288cca05481908faeb1563711114a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f27c9ddfcc819096697a844b300cce |
completed | April 29, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 17, 2026, 11:33 p.m.