Triple
T590449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of the Somme |
E17254
|
entity |
| Predicate | dateOfFirstTankUse |
P14226
|
FINISHED |
| Object | 1916-09-15 |
—
|
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-09-15 | Statement: [Battle of the Somme, dateOfFirstTankUse, 1916-09-15]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfFirstTankUse Context triple: [Battle of the Somme, dateOfFirstTankUse, 1916-09-15]
-
A.
firstCombatUseDate
chosen
Indicates the date on which something (typically a weapon, system, or tactic) was first used in actual combat.
-
B.
firstShotsFiredOn
Indicates that the referenced event or entity marks the initial occurrence of shots being fired on a specified date, time, or occasion.
-
C.
firstOperationalUse
Indicates the point in time or context when something is used operationally for the very first time.
-
D.
firstShotsFiredAt
Indicates the location or time at which the initial gunshots or opening fire in an incident occurred.
-
E.
firstUsedFor
Indicates that one entity was the earliest or original thing for which another entity was used or applied.
- 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_69a49379d09c8190ac7e00b24e2810b1 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49bb8ff0081909cd53d88930e2693 |
completed | March 1, 2026, 8:04 p.m. |
| PD | Predicate disambiguation | batch_69a494cc13988190892ca10bd7ae9f09 |
completed | March 1, 2026, 7:34 p.m. |
Created at: March 1, 2026, 7:33 p.m.