Triple
T32185668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Airman First Class (USSF enlisted rank) |
E822101
|
entity |
| Predicate | isSuperordinateTo |
P173624
|
FINISHED |
| Object | Airman (USSF enlisted rank) |
—
|
NE NERFINISHED |
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: Airman (USSF enlisted rank) | Statement: [Airman First Class (USSF enlisted rank), isSuperordinateTo, Airman (USSF enlisted rank)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSuperordinateTo Context triple: [Airman First Class (USSF enlisted rank), isSuperordinateTo, Airman (USSF enlisted rank)]
-
A.
isSuperiorOf
chosen
Indicates that one entity holds a higher rank, authority, or hierarchical position over another entity.
-
B.
isSupergroupOf
Indicates that one group contains another group as a proper subgroup, having strictly more members or elements than the other.
-
C.
isParentOf
Indicates that one entity is the biological or legal parent of another entity.
-
D.
isSubclusterOf
Indicates that one cluster is a smaller, contained subset within a larger cluster.
-
E.
isPartOfHierarchyWith
Indicates that one entity occupies a defined position within an ordered or nested structure relative to another entity in the same hierarchy.
- 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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bab9100c8190ad1f86fece0fc505 |
completed | May 3, 2026, 3:02 a.m. |
| PD | Predicate disambiguation | batch_69f6b6293188819080d5041ca0adb969 |
completed | May 3, 2026, 2:42 a.m. |
Created at: May 1, 2026, 12:35 a.m.