Triple
T4162687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | W. D. A. Lentaigne |
E91567
|
entity |
| Predicate | forceTypeCommanded |
P1062
|
FINISHED |
| Object | long-range penetration special force |
—
|
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: long-range penetration special force | Statement: [W. D. A. Lentaigne, forceTypeCommanded, long-range penetration special force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: forceTypeCommanded Context triple: [W. D. A. Lentaigne, forceTypeCommanded, long-range penetration special force]
-
A.
forceType
chosen
Indicates the specific kind or category of force involved in an interaction or event (e.g., physical, legal, military, or other defined force classifications).
-
B.
forceDirection
Indicates the direction in which a force is applied or exerted in the relationship between entities.
-
C.
commandedTo
Indicates that one entity has issued an order or directive for another entity to perform a specific action or fulfill a particular duty.
-
D.
commandedBy
Indicates that one entity holds authoritative control or issues orders over another entity.
-
E.
forceElement
Indicates a physical or conceptual force acting upon, influencing, or constraining another element within a system or interaction.
- 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_69aed9626ebc8190a39de631788bea3e |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0321eee88190871c1d4bf44a5007 |
completed | March 9, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69af018dc90c8190a754b1bfbc802e80 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:44 p.m.