Triple
T13682893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jump Week |
E328044
|
entity |
| Predicate | branchFocus |
P31
|
FINISHED |
| Object | Army airborne forces |
—
|
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: Army airborne forces | Statement: [Jump Week, branchFocus, Army airborne forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchFocus Context triple: [Jump Week, branchFocus, Army airborne forces]
-
A.
branchSpecific
Indicates that something is associated with, restricted to, or applicable only within a particular branch or subdivision of a larger organization or structure.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
branchLine
Indicates a relationship where one line, route, or path diverges from and is subordinate to a main or primary line.
-
D.
branchPosition
Indicates the relative location or placement of something along a branch.
-
E.
branchType
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
- 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_69d8076f1fa8819094664a59b55010df |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc66e75188190a9e82fdc5eb26513 |
completed | April 12, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:53 p.m.