Triple
T31014002
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Philippine Army Special Forces Regiment (Airborne) |
E790278
|
entity |
| Predicate | usesParachuteQualification |
P44086
|
FINISHED |
| Object | Airborne |
—
|
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: Airborne | Statement: [Philippine Army Special Forces Regiment (Airborne), usesParachuteQualification, Airborne]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesParachuteQualification Context triple: [Philippine Army Special Forces Regiment (Airborne), usesParachuteQualification, Airborne]
-
A.
parachuteStatus
Indicates the current condition or operational state of a parachute in relation to its use or deployment.
-
B.
parachuteType
Indicates the specific kind or category of parachute associated with an entity or event.
-
C.
parachuteSystem
Indicates that one entity functions as a parachute system used to safely decelerate or recover another entity.
-
D.
parachuteMass
Indicates the mass or weight associated with a parachute in the described context.
-
E.
usesQualificationSystem
chosen
Indicates that an entity applies or relies on a specific qualification system as part of its processes or operations.
- 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_69f224c73ca48190a1e46cb58ad4045b |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: April 29, 2026, 8:57 p.m.