Triple
T8423877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ASCOD Ulan |
E198927
|
entity |
| Predicate | transportCapacity |
P82100
|
FINISHED |
| Object | infantry squad with equipment |
—
|
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: infantry squad with equipment | Statement: [ASCOD Ulan, transportCapacity, infantry squad with equipment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transportCapacity Context triple: [ASCOD Ulan, transportCapacity, infantry squad with equipment]
-
A.
designedCargoCapacity
Indicates the maximum amount of cargo an object (such as a vehicle or container) was originally engineered or specified to carry.
-
B.
cargoCapacityFeature
Indicates that an entity has a feature specifying how much cargo it can carry or accommodate.
-
C.
maximumPassengerCapacity
Indicates the greatest number of passengers that an entity is designed or allowed to carry at one time.
-
D.
aircraftCapacity
Indicates the maximum number of passengers or amount of load that an aircraft is designed or allowed to carry.
-
E.
railCarries
Indicates that a rail or railway system transports or conveys a specified entity from one place to another.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb859f787481908a11797a317c8849 |
completed | March 31, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:07 p.m.