Triple
T34404422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Company A, 1st Battalion, 121st Infantry Regiment |
E883069
|
entity |
| Predicate | typicalBranchType |
P1988
|
FINISHED |
| Object | infantry |
—
|
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: infantry | Statement: [Company A, 1st Battalion, 121st Infantry Regiment, typicalBranchType, infantry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBranchType Context triple: [Company A, 1st Battalion, 121st Infantry Regiment, typicalBranchType, infantry]
-
A.
isPartOfBranchTypically
Indicates that something is typically a component or subdivision within a larger branch.
-
B.
branchType
chosen
Indicates the specific kind or category of branch that an entity belongs to or is associated with.
-
C.
typicalBureauType
Indicates that one entity is the standard or commonly occurring type or category of bureau associated with another entity.
-
D.
typicalSegmentType
Indicates that something is classified as belonging to a usual or characteristic type of segment within a broader structure or sequence.
-
E.
trainedBranch
Indicates that one entity has provided training or instruction to a specific branch or subdivision of 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_69f349c1f2208190a09a489bb8b2719d |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a037c8ae0248190b7e2ce4bf852c22d |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379fbe4a08190bfe65ebd141164e9 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:59 a.m.