Triple
T14281757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alferes |
E354064
|
entity |
| Predicate | typicalBranch |
P22486
|
FINISHED |
| Object | land 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: land forces | Statement: [Alferes, typicalBranch, land forces]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBranch Context triple: [Alferes, typicalBranch, land forces]
-
A.
isPartOfBranchTypically
chosen
Indicates that something is typically a component or subdivision within a larger branch.
-
B.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of another entity.
-
C.
uniformBranch
Indicates that multiple entities share the same branch, division, or organizational unit within a larger structure.
-
D.
typicalBase
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
-
E.
representedBranch
Indicates that one entity serves as a representative or proxy for a particular branch of another entity or 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_69d8278d25148190abf1a8c8f5f533ad |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de697b5e8081908e5b91a3a1c55df9 |
completed | April 14, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69de2a88446481909cd526da97a3b70f |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:10 a.m.