Triple
T31025185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habu missions |
E790548
|
entity |
| Predicate | associatedSquadron |
P13144
|
FINISHED |
| Object | 1st Strategic Reconnaissance Squadron |
E688736
|
NE 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: 1st Strategic Reconnaissance Squadron | Statement: [Habu missions, associatedSquadron, 1st Strategic Reconnaissance Squadron]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedSquadron Context triple: [Habu missions, associatedSquadron, 1st Strategic Reconnaissance Squadron]
-
A.
squadron
chosen
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
B.
squadronCode
Indicates the identifying code assigned to a military or aviation squadron that denotes its unit designation.
-
C.
associatedClan
Indicates a relationship where an entity is linked or belongs to a particular clan, group, or lineage.
-
D.
squadronSystem
Indicates a relationship where an entity functions as or is part of the system, organization, or structure associated with a particular squadron.
-
E.
associatedTeam
Indicates that one entity is linked or connected to a particular team, typically as its member, owner, or primary affiliation.
- F. None of above.
Provenance (4 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_69f224c811508190a7de096a5b1f5798 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a29470bdfa481909e1fb992f0a3af26 |
completed | June 10, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:58 p.m.