Triple
T2030611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 3rd Canadian Division |
E44506
|
entity |
| Predicate | firstSawAction |
P34730
|
FINISHED |
| Object | 1916 |
—
|
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: 1916 | Statement: [3rd Canadian Division, firstSawAction, 1916]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSawAction Context triple: [3rd Canadian Division, firstSawAction, 1916]
-
A.
firstDemonstrated
Indicates that one entity was the earliest to show, prove, or exemplify a particular concept, method, or capability in relation to another entity or context.
-
B.
firstAppeared
Indicates the earliest known time or context in which an entity was introduced, observed, or came into existence.
-
C.
firstMission
Indicates that an entity is undertaking or associated with its initial mission or assignment in a given context.
-
D.
firstAVA
Indicates that the subject is the first entity (e.g., version, appearance, or instance) in a sequence associated with the object.
-
E.
wasFirst
Indicates that one entity occurred, appeared, or held a position before another in time or sequence.
- F. None of above. chosen
Provenance (4 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_69a889144f2481909932f0746a93023d |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb915c9548190809d08c4d67466fb |
completed | March 7, 2026, 5:35 a.m. |
| PD | Predicate disambiguation | batch_69abb7a656248190ac2ced196b35bc6b |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb85fe7a08190b991b1f23bc34f93 |
completed | March 7, 2026, 5:32 a.m. |
Created at: March 4, 2026, 7:38 p.m.