Triple
T9298421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waco CG-4 |
E223697
|
entity |
| Predicate | capacityTroops |
P17501
|
FINISHED |
| Object | 13 fully equipped troops |
—
|
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: 13 fully equipped troops | Statement: [Waco CG-4, capacityTroops, 13 fully equipped troops]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: capacityTroops Context triple: [Waco CG-4, capacityTroops, 13 fully equipped troops]
-
A.
paratroopCapacity
chosen
Indicates the maximum number of paratroopers or amount of airborne troops that something (typically a vehicle or vessel) is capable of carrying or deploying.
-
B.
canCarryTroops
Indicates that an entity has the capability to transport troops from one location to another.
-
C.
typeOfTroops
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
-
D.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
E.
armamentCapacity
Indicates the maximum quantity or type of weapons or munitions that something is designed or allowed to carry.
- 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_69ca8423edb08190bc0c91287a484768 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd08cf50cc8190a025f478dff4f9fd |
completed | April 1, 2026, noon |
| PD | Predicate disambiguation | batch_69cc7a5ef1908190bc5ca166bb895af6 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:36 p.m.