Triple
T1765784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | General |
E38759
|
entity |
| Predicate | foundInBranch |
P6271
|
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: [General, foundInBranch, army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: foundInBranch Context triple: [General, foundInBranch, army]
-
A.
usedByBranch
Indicates that something (such as a resource, configuration, or component) is utilized or depended upon by a particular branch.
-
B.
involvedBranch
chosen
Indicates that a particular branch (such as a location, division, or sub-unit) participates in, is associated with, or plays a role in the referenced event, process, or relationship.
-
C.
branchesFrom
Indicates that one entity originates or diverges from another as a subordinate or offshoot path, structure, or lineage.
-
D.
parentBranch
Indicates that one branch serves as the direct ancestor or source from which another branch originates or is derived.
-
E.
possibleBranch
Indicates that one entity can serve as an alternative or potential continuation path branching from another entity.
- 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab39fc2c448190bfaf1ee8d474632a |
completed | March 6, 2026, 8:33 p.m. |
| PD | Predicate disambiguation | batch_69aa61cbb1288190a7ba38b61905f578 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.