Triple
T34941738
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Dutchman |
E1007739
|
entity |
| Predicate | hasLanguageOfEarliestAccounts |
P3926
|
FINISHED |
| Object | Dutch |
—
|
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: Dutch | Statement: [Flying Dutchman, hasLanguageOfEarliestAccounts, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfEarliestAccounts Context triple: [Flying Dutchman, hasLanguageOfEarliestAccounts, Dutch]
-
A.
languageOfEarliestForm
chosen
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
B.
languageAttestedIn
Indicates that evidence exists showing the use or presence of a particular language in a specified place, time, or context.
-
C.
historicalLanguageOfBearers
Indicates that the specified language is historically spoken or used by the bearers of a given name, title, or designation.
-
D.
historicallySpokenIn
Indicates that a language was used for spoken communication in a particular place or region during a past historical period.
-
E.
languageOfHistoricalRecord
Indicates the language in which a given historical record is written or recorded.
- 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_69f76dc513fc819084a1ff52abbfa5bc |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 3, 2026, 4 p.m.