Triple
T38541887
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSE:SAB |
E924853
|
entity |
| Predicate | hadUnderlyingCompanyHeadquartersIn |
P46909
|
FINISHED |
| Object | London |
—
|
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: London | Statement: [JSE:SAB, hadUnderlyingCompanyHeadquartersIn, London]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadUnderlyingCompanyHeadquartersIn Context triple: [JSE:SAB, hadUnderlyingCompanyHeadquartersIn, London]
-
A.
hasManufacturerHeadquartersIn
Indicates that the location specified is the place where the manufacturer’s main headquarters is situated.
-
B.
hasOrHadHeadquartersIn
chosen
Indicates that an organization currently has, or previously had, its main headquarters located in a specified place.
-
C.
hasHeadquartersOn
Indicates that an organization’s main headquarters is located on a specified street, road, or similar thoroughfare.
-
D.
hasHeadquartersOfFoundedCompanyIn
Indicates that the headquarters of a company is located in a place where that company was originally founded.
-
E.
hasHeadquartersBuildingIn
Indicates that an organization’s main headquarters building is physically located in a specified place.
- 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_69f76eadeac081909cdfdd0474cb6765 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fcd2eb85e4819088eb5a8fc4d4f668 |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f81cbc8190b4fd3bfc3106c1f3 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.