Triple
T18595476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tharangambadi |
E454482
|
entity |
| Predicate | danishControlStartYear |
P66904
|
FINISHED |
| Object | 1620 |
—
|
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: 1620 | Statement: [Tharangambadi, danishControlStartYear, 1620]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: danishControlStartYear Context triple: [Tharangambadi, danishControlStartYear, 1620]
-
A.
timePeriodAsDanishTerritory
chosen
Indicates that, during a specified time period, the referenced place or region was under Danish territorial control or sovereignty.
-
B.
beganInYear
Indicates that an event, process, or state started in a specific calendar year.
-
C.
settingStartYear
Indicates the year in which a particular setting, configuration, or condition first becomes effective or begins to apply.
-
D.
firstRunningYear
Indicates the year in which something (such as an event, service, or operation) first began running or was initially active.
-
E.
typicalStartYear
Indicates the year in which something (such as an event, activity, or process) usually or customarily begins.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e545ba3bc881908f5308e09d54e05b |
completed | April 19, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:44 a.m.