Triple
T37694418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpine Div. |
E938888
|
entity |
| Predicate | hasTypicalBranch |
P22486
|
FINISHED |
| Object | army |
—
|
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 | Statement: [Alpine Div., hasTypicalBranch, army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBranch Context triple: [Alpine Div., hasTypicalBranch, army]
-
A.
isPartOfBranchTypically
chosen
Indicates that something is typically a component or subdivision within a larger branch.
-
B.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
C.
hasBranchCharacteristic
Indicates that a branch of an entity possesses a specified characteristic or property.
-
D.
hasMajorBranch
Indicates that one entity possesses or includes another entity as a primary or principal subdivision or branch.
-
E.
hasTwoBranches
Indicates that the related entity is divided into or composed of exactly two distinct branches.
- 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_69f76eda6ae48190b3111071eeacc038 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: May 3, 2026, 4:18 p.m.