Triple
T11117095
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zoutkamp |
E262913
|
entity |
| Predicate | hasPrimaryCharacter |
P97041
|
FINISHED |
| Object | maritime village |
—
|
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: maritime village | Statement: [Zoutkamp, hasPrimaryCharacter, maritime village]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCharacter Context triple: [Zoutkamp, hasPrimaryCharacter, maritime village]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasPrimary
Indicates that one entity is designated as the main or most important instance (the primary) in relation to another entity.
-
C.
hasPrimaryKami
Indicates that an entity is associated with or devoted to a specific main kami (deity) as its primary spiritual focus or guardian.
-
D.
hasMainRole
Indicates that an entity holds the primary or most significant role in relation to another entity or context.
-
E.
hasMainThemeCharacter
Indicates that a work (such as a story, film, or game) features a specific character as its central or primary thematic focus.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79af638b08190b7ade5eb0cab6b75 |
completed | April 9, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750cb26f48190a134614d0aa8e283 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.