Triple
T29927842
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States military installations in Maryland |
E760131
|
entity |
| Predicate | branchPresence |
P51210
|
FINISHED |
| Object | United States Army |
—
|
NE NERFINISHED |
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: United States Army | Statement: [United States military installations in Maryland, branchPresence, United States Army]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: branchPresence Context triple: [United States military installations in Maryland, branchPresence, United States Army]
-
A.
presentInBranch
chosen
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
B.
branchLocation
Indicates the physical or geographical location where a particular branch of an organization or structure is situated.
-
C.
branchPosition
Indicates the relative location or placement of something along a branch.
-
D.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
E.
branchChecked
Indicates that a specific branch (such as in version control or a decision tree) has been examined or verified.
- 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_69f224631674819080c8d089674f9f4f |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f677cdf7c081908af7be4259c7c615 |
completed | May 2, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69f66ec8298c8190b41fe9d182c05676 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:16 p.m.