Triple
T24174212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Spaanse Rijk |
E599229
|
entity |
| Predicate | belangrijkeHaven |
P115895
|
FINISHED |
| Object | Sevilla |
E359506
|
NE 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: Sevilla | Statement: [Spaanse Rijk, belangrijkeHaven, Sevilla]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: belangrijkeHaven Context triple: [Spaanse Rijk, belangrijkeHaven, Sevilla]
-
A.
isMainHarbourOf
Indicates that a harbour serves as the primary or principal port facility for a specified location or region.
-
B.
harbours
Indicates that one entity provides shelter, refuge, or concealment for another, often by keeping it safe or hidden.
-
C.
harbourName
Indicates the name assigned to a harbour in which an entity is located or associated.
-
D.
associatedHarbour
chosen
Indicates a relationship where a place, route, or maritime entity is linked to or served by a particular harbour.
-
E.
harbourSide
Indicates a location or object that is situated alongside or directly adjacent to a harbour.
- F. None of above.
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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10759fb6bc8190a5f1c2ec2f2dca6a |
completed | May 22, 2026, 3:26 p.m. |
| PD | Predicate disambiguation | batch_69f1c42f942c8190b103ff29a60fef34 |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 17, 2026, 11:33 p.m.