Triple
T31503672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 13th Royal Württemberg Army Corps |
E803755
|
entity |
| Predicate | includedArm |
P21872
|
FINISHED |
| Object | artillery |
—
|
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: artillery | Statement: [13th Royal Württemberg Army Corps, includedArm, artillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedArm Context triple: [13th Royal Württemberg Army Corps, includedArm, artillery]
-
A.
includesArm
Indicates that one entity contains, incorporates, or has an arm as a component or part of itself.
-
B.
hasArm
chosen
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
-
C.
isDistributionArmOf
Indicates that one entity functions as the distribution arm or channel responsible for delivering or selling the products or services of another entity.
-
D.
armsIncorporatedIn
Indicates that one entity’s arms or armorial bearings are formally included within, or combined into, the heraldic arms of another entity.
-
E.
includedSingle
Indicates that one specific, individual item is contained within or made part of another set, group, or collection.
- 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_69f348cae52081909fa8e5f697523ae3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a013f09b0988190ba3179c7d56c726a |
completed | May 11, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_6a013e600e248190a1a9c363702c8586 |
completed | May 11, 2026, 2:26 a.m. |
Created at: April 30, 2026, 9:46 p.m.