Triple
T159326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander-in-Chief of the Continental Army |
E3245
|
entity |
| Predicate | commandScope |
P6856
|
FINISHED |
| Object | land forces of the Continental Army |
—
|
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: land forces of the Continental Army | Statement: [Commander-in-Chief of the Continental Army, commandScope, land forces of the Continental Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commandScope Context triple: [Commander-in-Chief of the Continental Army, commandScope, land forces of the Continental Army]
-
A.
commands
Indicates that one entity holds authority over another and issues directives or orders that the other is expected to follow.
-
B.
commandsThrough
Indicates that one entity exercises authority or control over another indirectly, acting through an intermediary or chain of command.
-
C.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
D.
commandSetUsedBy
Indicates that a particular command set is utilized or referenced by a given entity or system.
-
E.
commander
Indicates that one entity holds authoritative military or organizational control over another entity or group.
- F. None of above. chosen
Provenance (4 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a25855baf48190a1b63f2e5865d957 |
completed | Feb. 28, 2026, 2:52 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.