Triple
T7487663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Amiens (1918) |
E176921
|
entity |
| Predicate | tanksUsed |
P5289
|
FINISHED |
| Object | over 400 Allied tanks |
—
|
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: over 400 Allied tanks | Statement: [Battle of Amiens (1918), tanksUsed, over 400 Allied tanks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tanksUsed Context triple: [Battle of Amiens (1918), tanksUsed, over 400 Allied tanks]
-
A.
numberOfTanks
chosen
Indicates the quantity or count of tanks associated with a given entity or context.
-
B.
artilleryUsedBy
Indicates that a particular artillery asset is operated or employed by a specified user, such as a military unit, organization, or country.
-
C.
mainTankCapacity
Indicates the maximum volume of fuel or liquid that the primary tank is designed to hold.
-
D.
numberOfMainBatteryGuns
Indicates the quantity of primary (main) battery guns that an entity, typically a warship or similar platform, is equipped with.
-
E.
hasTank
Indicates that an entity possesses, is equipped with, or contains a tank (such as a storage tank, fuel tank, or similar vessel).
- 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_69c69f24ac508190bb98fe927c0bd065 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f55965ac81909d3c3a5422b22d44 |
completed | March 27, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69c6f03eeaa88190a5215772ed05ee9f |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:43 p.m.