Triple
T35410798
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Richard Ruoff |
E1023504
|
entity |
| Predicate | wasInCommandOf |
P7176
|
FINISHED |
| Object | III Army Corps |
—
|
NE NERFINISHED |
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: III Army Corps | Statement: [Richard Ruoff, wasInCommandOf, III Army Corps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasInCommandOf Context triple: [Richard Ruoff, wasInCommandOf, III Army Corps]
-
A.
capturedUnderCommandOf
Indicates that one entity was captured while operating under the authority, leadership, or command of another entity.
-
B.
commandedIn
chosen
Indicates that one entity held a position of command or leadership within a specified context, such as a battle, operation, or organization.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
wasCommandantOf
Indicates that one entity served as the commandant (chief commanding officer) of another entity, typically a military unit, institution, or facility.
-
E.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
- 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_69f76df54bac8190bd0d3b0eb35cda5f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795672b40819087ccce744e044124 |
completed | May 3, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4:03 p.m.