Triple
T19778749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delta (USSF organizational echelon) |
E475076
|
entity |
| Predicate | hasStaffFunctions |
P63628
|
FINISHED |
| Object | operations |
—
|
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: operations | Statement: [Delta (USSF organizational echelon), hasStaffFunctions, operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStaffFunctions Context triple: [Delta (USSF organizational echelon), hasStaffFunctions, operations]
-
A.
hadStaffRole
Indicates that an entity served in a specific staff role or position for another entity during some period.
-
B.
hasBackOfficeFunctionsIn
Indicates that an entity’s back-office operations or support functions are performed or located in a specified place or organizational unit.
-
C.
hasGeneralStaff
chosen
Indicates that an entity has, is associated with, or is served by a general staff body responsible for overall strategic or administrative functions.
-
D.
hasAdultStaffRole
Indicates that an entity holds a staff position or role designated specifically for adults.
-
E.
hasSupportStaff
Indicates that an entity is associated with one or more staff members who provide assistance or support services to it.
- 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_69d8e51a43a08190956bc6df13c91a77 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538230488190b45cd8aaec658f7f |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.