Triple
T28230766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Private London |
E711722
|
entity |
| Predicate | featuresBranchOfAgency |
P116110
|
FINISHED |
| Object | Private London branch |
—
|
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: Private London branch | Statement: [Private London, featuresBranchOfAgency, Private London branch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresBranchOfAgency Context triple: [Private London, featuresBranchOfAgency, Private London branch]
-
A.
serviceBranch
Indicates the military or organizational branch in which an entity serves or is affiliated.
-
B.
associatedOrganizationBranch
chosen
Indicates that an entity is connected to or linked with a specific branch or subdivision of an organization.
-
C.
serviceBranchLevel
Indicates the hierarchical level or tier within a service branch at which an entity operates or is classified.
-
D.
serviceBranchFeature
Indicates that a particular feature, capability, or characteristic is associated with or provided by a specific branch of service.
-
E.
serviceBranchComposition
Indicates the relationship between a military service branch and the types or proportions of personnel or units that make up its overall composition.
- 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_69efb51ece308190b8c269a057e36652 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69fe68a4b67881909ca1d9f276f922e0 |
completed | May 8, 2026, 10:50 p.m. |
| PD | Predicate disambiguation | batch_69fe680234c88190b01f953987b74972 |
completed | May 8, 2026, 10:47 p.m. |
Created at: April 27, 2026, 10:52 p.m.