Triple
T24866175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Burma Camp, Accra |
E622288
|
entity |
| Predicate | hasBranchPresence |
P51210
|
FINISHED |
| Object | Ghana Navy |
—
|
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: Ghana Navy | Statement: [Burma Camp, Accra, hasBranchPresence, Ghana Navy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBranchPresence Context triple: [Burma Camp, Accra, hasBranchPresence, Ghana Navy]
-
A.
hasBranchName
Indicates that an entity (such as a branch or subdivision) bears or is identified by a specific branch name.
-
B.
hasStateBranch
Indicates that one entity functions as a branch, subdivision, or local office of a larger parent entity within a particular state or regional jurisdiction.
-
C.
hasBranches
Indicates that an entity extends into multiple subordinate parts or offshoots, like limbs, divisions, or sections stemming from a main source.
-
D.
presentInBranch
chosen
Indicates that something exists or is available within a specific branch or subdivision of a larger organization or structure.
-
E.
hasElevatedBranch
Indicates that one entity possesses or features a branch that is positioned higher or raised relative to a reference level or structure.
- 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_69e2fac350d08190b3affde1b451a8c5 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:22 a.m.