Triple
T16178945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holden HT |
E392636
|
entity |
| Predicate | hasVariant |
P455
|
FINISHED |
| Object | Brougham |
E855904
|
NE 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: Brougham | Statement: [Holden HT, hasVariant, Brougham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brougham Context triple: [Holden HT, hasVariant, Brougham]
-
A.
Brougham
Brougham is a small village and civil parish in Cumbria, England, known for its historic castle and proximity to the town of Penrith.
-
B.
Brougham
Brougham is a small historic community and neighbourhood within the City of Pickering in Ontario, Canada.
-
C.
Brougham
chosen
Brougham is a luxury-oriented trim level name historically used by American automakers to denote more upscale interior and comfort features on certain models.
-
D.
Brougham Villiers
Brougham Villiers is a notable member of the Villiers family, recognized primarily for his association with the prominent Villiers lineage.
-
E.
Royal Brougham
Royal Brougham was a prominent Seattle sportswriter and editor known for his long career at the Seattle Post-Intelligencer and his significant influence on the city's sports culture.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e2205ab3108190a84fc2dfe61d5044 |
completed | April 17, 2026, 11:58 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fffefe4dc08190a6cc43a448ae6554 |
completed | May 10, 2026, 3:43 a.m. |
Created at: April 10, 2026, 5:02 a.m.