Triple
T31503671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 13th Royal Württemberg Army Corps |
E803755
|
entity |
| Predicate | standardArm |
P22039
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [13th Royal Württemberg Army Corps, standardArm, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardArm Context triple: [13th Royal Württemberg Army Corps, standardArm, infantry]
-
A.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
B.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
C.
laterArm
Indicates that one event, state, or action occurs at a later time than another within the same arm or branch of a process or study.
-
D.
armType
chosen
Indicates the specific kind or configuration of an arm associated with an entity.
-
E.
hasArm
Indicates that one entity possesses or is equipped with an arm as a physical part or component of itself.
- 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_69f7688dd3d08190ad13d0e780570a1c |
completed | May 3, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_69f767fcf2f881908bacc7bfc38e68a5 |
completed | May 3, 2026, 3:21 p.m. |
Created at: April 30, 2026, 9:46 p.m.