Triple
T15395652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Dutch Church |
E368169
|
entity |
| Predicate | hasLanguageOfEarlyRecords |
P30358
|
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: [Old Dutch Church, hasLanguageOfEarlyRecords, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLanguageOfEarlyRecords Context triple: [Old Dutch Church, hasLanguageOfEarlyRecords, Dutch]
-
A.
languageOfEarliestForm
Indicates the language in which the earliest known form or attested version of something (e.g., a text, name, or expression) is recorded.
-
B.
languageOfHistoricalRecord
chosen
Indicates the language in which a given historical record is written or recorded.
-
C.
hasMajorityLanguageHistorically
Indicates that a particular language has historically been the predominant or majority language within a given entity or region.
-
D.
hasLanguageEvidenceOf
Indicates that there is linguistic or textual evidence supporting, documenting, or attesting to the related entity or claim.
-
E.
languageAttestedIn
Indicates that evidence exists showing the use or presence of a particular language in a specified place, time, or context.
- 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_69d85a16c68c819099c1b547fbc87b32 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e8ac79081908ac79c0b3e7587ff |
completed | April 16, 2026, 1:42 a.m. |
| PD | Predicate disambiguation | batch_69ded27b8cac8190bfa77698d53c5d1c |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:19 a.m.