Triple
T50588
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dutch East India Company |
E992
|
entity |
| Predicate | charterGranted |
P2246
|
FINISHED |
| Object | 1602 |
—
|
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: 1602 | Statement: [Dutch East India Company, charterGranted, 1602]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charterGranted Context triple: [Dutch East India Company, charterGranted, 1602]
-
A.
styleGranted
Indicates that a particular style, manner, or mode of expression has been conferred or authorized for use by one entity to another.
-
B.
grantedBy
chosen
Indicates that a right, permission, or benefit is conferred or authorized by one entity to another.
-
C.
charteredIn
Indicates that an organization or entity has been formally established, authorized, or incorporated within a specified jurisdiction or location.
-
D.
hasCharterPurpose
Indicates that an entity’s purpose or mission, as formally defined in its charter or founding document, is the specified objective or activity.
-
E.
isCharterMemberOf
Indicates that an entity is an original or founding member of a group, organization, or institution at the time it was established.
- 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_69a2480baefc81909951b14058479aa2 |
completed | Feb. 28, 2026, 1:42 a.m. |
| NER | Named-entity recognition | batch_69a24ba7016481909d595402712db6e2 |
completed | Feb. 28, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69a24ac23f04819080cef9365ed990d4 |
completed | Feb. 28, 2026, 1:54 a.m. |
Created at: Feb. 28, 2026, 1:47 a.m.