Triple
T5648747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luigi Cadorna |
E124447
|
entity |
| Predicate | styleOfCommand |
P48303
|
FINISHED |
| Object | rigid discipline |
—
|
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: rigid discipline | Statement: [Luigi Cadorna, styleOfCommand, rigid discipline]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: styleOfCommand Context triple: [Luigi Cadorna, styleOfCommand, rigid discipline]
-
A.
commandStyle
chosen
Indicates the manner or approach in which one entity issues commands or directives to another.
-
B.
operatorStyle
Indicates the manner or approach an operator uses to perform or manage an operation, such as their method, technique, or behavioral style in carrying out tasks.
-
C.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
D.
commandOf
Indicates that one entity holds authoritative control or leadership over another, typically in a military, organizational, or hierarchical context.
-
E.
commandType
Indicates the specific kind or category of command being issued or executed in the relationship.
- 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_69c00825df388190a58742fa9b1aa33d |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022d1534c8190ac4828e44300fb91 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:42 p.m.