Triple
T35035320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holland Land Company |
E1010893
|
entity |
| Predicate | languageOfManagement |
P51016
|
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: [Holland Land Company, languageOfManagement, Dutch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfManagement Context triple: [Holland Land Company, languageOfManagement, Dutch]
-
A.
languageOfCurrentAdministration
Indicates the language currently used by the governing or administrative authority in charge.
-
B.
languageOfCommunications
Indicates that a specified language is used as the medium for communications associated with an entity or interaction.
-
C.
standardLanguageOf
Indicates that one entity serves as the officially recognized or commonly used standard language for another entity (such as a country, region, or organization).
-
D.
languageOfLocalOrganization
chosen
Indicates the language used or officially adopted by a local organization in its operations or communications.
-
E.
languageOfProvision
Indicates the language in which a provision, such as a legal or contractual clause, is written or officially expressed.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 3, 2026, 4:01 p.m.