Triple
T27822988
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frederiksnagore |
E702871
|
entity |
| Predicate | regionDuringDanishRule |
P66904
|
FINISHED |
| Object | Hooghly district |
—
|
NE NERFINISHED |
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: Hooghly district | Statement: [Frederiksnagore, regionDuringDanishRule, Hooghly district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regionDuringDanishRule Context triple: [Frederiksnagore, regionDuringDanishRule, Hooghly district]
-
A.
timePeriodAsDanishTerritory
chosen
Indicates that, during a specified time period, the referenced place or region was under Danish territorial control or sovereignty.
-
B.
wasUnderSwedishRuleFrom
Indicates that one entity was governed or controlled by Sweden during a specified time period.
-
C.
ruledFromCentury
Indicates that a ruling or governance relationship is associated with a specific century during which it took place.
-
D.
functionDuringDanishRule
Indicates that a function, role, or activity was performed or existed during the period of Danish rule.
-
E.
ruledUntilCentury
Indicates that a ruling relationship held by an entity continued in effect up to (but not necessarily including) a specified century.
- 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_69ef840ad1e88190b5bff2d1ddec8700 |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 27, 2026, 5:49 p.m.