Triple
T24174216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaanse Rijk |
E599229
|
entity |
| Predicate | belangrijkeVloot |
P4689
|
FINISHED |
| Object | Spaanse Armada |
—
|
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: Spaanse Armada | Statement: [Spaanse Rijk, belangrijkeVloot, Spaanse Armada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belangrijkeVloot Context triple: [Spaanse Rijk, belangrijkeVloot, Spaanse Armada]
-
A.
navalFleet
chosen
Indicates a relationship where multiple naval vessels are organized and operate together as a coordinated maritime military force.
-
B.
fleetFlagshipOf
Indicates that one entity serves as the primary or leading flagship of a particular fleet.
-
C.
fleetCommander
Indicates that one entity serves as the commanding officer or overall leader in charge of the operations and decisions of a fleet associated with another entity.
-
D.
garrisonVessel
Indicates that a vessel is stationed at or assigned to serve as a garrison or defensive presence at a particular location.
-
E.
squadronFlagshipOf
Indicates that one entity serves as the primary or lead flagship vessel of a particular squadron.
- 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_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. |
Created at: April 17, 2026, 11:33 p.m.