Triple
T36148739
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Battalion, 504th Parachute Infantry Regiment |
E1045524
|
entity |
| Predicate | usesParachuteInsertion |
P192328
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [1st Battalion, 504th Parachute Infantry Regiment, usesParachuteInsertion, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesParachuteInsertion Context triple: [1st Battalion, 504th Parachute Infantry Regiment, usesParachuteInsertion, yes]
-
A.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover another entity.
-
B.
parachuteSystemCompatible
Indicates that one system or component is suitable and safe for use with a specified parachute system, meeting required compatibility conditions.
-
C.
parachuteType
Indicates the specific kind or category of parachute associated with an entity or event.
-
D.
parachuteMass
Indicates the mass or weight associated with a parachute in the described context.
-
E.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
- 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_69f76e37ace88190a906b107d388f5d1 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
| PDg | Predicate description generation | batch_69fd05b965608190a3666410b9f8e125 |
completed | May 7, 2026, 9:35 p.m. |
Created at: May 3, 2026, 4:08 p.m.