Triple
T5118255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airborne and Ranger Training Brigade |
E115390
|
entity |
| Predicate | notableQualification |
P24944
|
FINISHED |
| Object | Ranger Tab |
—
|
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: Ranger Tab | Statement: [Airborne and Ranger Training Brigade, notableQualification, Ranger Tab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableQualification Context triple: [Airborne and Ranger Training Brigade, notableQualification, Ranger Tab]
-
A.
hasQualification
chosen
Indicates that an entity possesses a specific qualification, credential, or competency.
-
B.
notableFor
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
C.
notableCriterion
Indicates that something is distinguished or recognized based on a particular standard, measure, or qualifying condition.
-
D.
notableField
Indicates the field, discipline, or area of activity for which an entity is especially known or distinguished.
-
E.
notablePass
Indicates that one entity is recognized for having successfully passed or cleared another entity, such as a test, threshold, or evaluation, in a notably significant way.
- 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_69bd4442ade0819087b9461f892b206b |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7d5a23908190a24e79d1b29d6fcf |
completed | March 20, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69bd77aa68b88190a50dd736a72d2901 |
completed | March 20, 2026, 4:36 p.m. |
Created at: March 20, 2026, 1:41 p.m.