Triple
T14878267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mark II |
E349924
|
entity |
| Predicate | combatReadiness |
P116170
|
FINISHED |
| Object | limited |
—
|
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: limited | Statement: [Mark II, combatReadiness, limited]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combatReadiness Context triple: [Mark II, combatReadiness, limited]
-
A.
sustainmentCapability
Indicates the ability or resources required to maintain and support an operation, system, or activity over time.
-
B.
militaryBranchPreparedFor
Indicates that a specific military branch is organized, equipped, and trained to respond to or engage in a particular mission, operation, or type of conflict.
-
C.
warfareCapability
Indicates the ability or capacity of an entity to engage in, conduct, or support acts of warfare.
-
D.
combatArm
Indicates that one entity serves as a primary fighting or operational warfare branch or component of another entity (such as an organization or military force).
-
E.
combatantStrength
Indicates the relative level of power, capability, or effectiveness one combatant has in a conflict or confrontation compared to others.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded5e4e4448190a8796573bc6d1069 |
completed | April 15, 2026, 12:03 a.m. |
| PD | Predicate disambiguation | batch_69de8c1a2bcc81908f914e2e2ced65eb |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4c76e481909c0aa8d1a978e8d5 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:55 a.m.