Triple
T32902583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | the Dutchman |
E841650
|
entity |
| Predicate | canComeAshore |
P175561
|
FINISHED |
| Object | once every seven years |
—
|
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: once every seven years | Statement: [the Dutchman, canComeAshore, once every seven years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canComeAshore Context triple: [the Dutchman, canComeAshore, once every seven years]
-
A.
hasAmphibiousCapability
Indicates that an entity possesses the ability to operate effectively in both water and land environments.
-
B.
canSail
Indicates that an entity has the ability or permission to operate or travel by a sailing vessel.
-
C.
hasShoreOn
Indicates that one geographic entity borders or is directly adjacent to the shore of another body of water.
-
D.
amphibiousCapacity
Indicates the ability of an entity to operate effectively in both water and on land.
-
E.
hasStructureOnShore
Indicates that a structure is located on or directly adjacent to the shore of a body of water.
- 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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d210fc80819091ed8961aa2cddfb |
completed | May 3, 2026, 4:41 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
| PDg | Predicate description generation | batch_69f6d16b79dc8190ab0d4657f2ef9a5b |
completed | May 3, 2026, 4:39 a.m. |
Created at: May 1, 2026, 1:19 a.m.