Triple
T24137931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 27th Aero Squadron |
E598139
|
entity |
| Predicate | militaryBranchPredecessor |
P137432
|
FINISHED |
| Object | United States Army |
—
|
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: United States Army | Statement: [27th Aero Squadron, militaryBranchPredecessor, United States Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryBranchPredecessor Context triple: [27th Aero Squadron, militaryBranchPredecessor, United States Army]
-
A.
militaryBranchPredecessorOf
chosen
Indicates that one military branch served as the organizational or historical predecessor to another military branch.
-
B.
militaryBranchAssociatedWith
Indicates a relationship where an entity is connected to, or operates as part of, a specific branch of a military organization.
-
C.
militaryBranchComponentOf
Indicates that one military branch or unit is an organizational component or subordinate part of a larger military branch or force.
-
D.
militaryBranchTransition
Indicates a change in an entity’s affiliation from one military branch to another.
-
E.
militaryBranchPrecedence
Indicates the relative order of importance or seniority among different branches of a military organization.
- 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_69e288c92e448190ac57034fa0c863ce |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1df7e3c20819099ff289789829d7e |
completed | April 29, 2026, 10:37 a.m. |
| PD | Predicate disambiguation | batch_69f1765650fc8190a6bc1eb512b240bf |
completed | April 29, 2026, 3:09 a.m. |
Created at: April 17, 2026, 11:27 p.m.