Triple
T26704760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | British Tanganyika |
E673259
|
entity |
| Predicate | startDateAsTrustTerritory |
P288
|
FINISHED |
| Object | 1946 |
—
|
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: 1946 | Statement: [British Tanganyika, startDateAsTrustTerritory, 1946]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: startDateAsTrustTerritory Context triple: [British Tanganyika, startDateAsTrustTerritory, 1946]
-
A.
startDateAsGuerrilla
Indicates the date on which an entity began operating or acting in a guerrilla capacity.
-
B.
startDate
chosen
Indicates the point in time when an event, state, or relationship begins.
-
C.
startDateRule
Indicates the rule or condition that determines when something is allowed or required to start.
-
D.
startDateNewStyle
Indicates the date on which something begins, expressed according to the New Style (Gregorian) calendar rather than the Old Style (Julian) calendar.
-
E.
startDateConstraint
Indicates a restriction or condition placed on when something is allowed to start, typically specifying valid or required start dates.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7764ab1fc81909f9348db87bd7692 |
completed | May 3, 2026, 4:22 p.m. |
| PD | Predicate disambiguation | batch_69f76905d9c88190b1ee810bc9ab644f |
completed | May 3, 2026, 3:25 p.m. |
Created at: April 27, 2026, 3:33 a.m.