Triple
T10887842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1st Parachute Battalion (USMC) |
E257094
|
entity |
| Predicate | parachuteQualified |
P74646
|
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 Parachute Battalion (USMC), parachuteQualified, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: parachuteQualified Context triple: [1st Parachute Battalion (USMC), parachuteQualified, yes]
-
A.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
-
B.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover another entity.
-
C.
airborneQualified
chosen
Indicates that an entity has successfully completed airborne training and is certified or qualified to conduct airborne (parachute) operations.
-
D.
hasQualification
Indicates that an entity possesses a specific qualification, credential, or competency.
-
E.
equippedFor
Indicates that one entity is suitably provided with the necessary tools, features, or capabilities to perform a particular function or handle a specific situation for another entity or purpose.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75201e6888190a2bc41a17784eec3 |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.