Triple
T34941739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Flying Dutchman |
E1007739
|
entity |
| Predicate | hasLanguageOfEarlyAccounts |
P3926
|
FINISHED |
| Object | English |
—
|
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: English | Statement: [Flying Dutchman, hasLanguageOfEarlyAccounts, English]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfEarlyAccounts Context triple: [Flying Dutchman, hasLanguageOfEarlyAccounts, English]
-
A.
languageInPreColumbianTimes
Indicates that a language was used or existed in a particular place or context during pre-Columbian times, i.e., before European contact with the Americas.
-
B.
languageAttestedIn
Indicates that evidence exists showing the use or presence of a particular language in a specified place, time, or context.
-
C.
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.
-
D.
hasLanguageOfArchaeologicalInterpretation
Indicates that an entity uses or is associated with a particular language in which archaeological findings or data are interpreted or described.
-
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_69ff63225b6481909217ad11b4f7d3ba |
completed | May 9, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ff60e0882c819085d097010db43ee0 |
completed | May 9, 2026, 4:29 p.m. |
Created at: May 3, 2026, 4 p.m.