Triple
T11020695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statesman |
E260479
|
entity |
| Predicate | coverBusiness |
P94881
|
FINISHED |
| Object | whiskey distillery |
—
|
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: whiskey distillery | Statement: [Statesman, coverBusiness, whiskey distillery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coverBusiness Context triple: [Statesman, coverBusiness, whiskey distillery]
-
A.
businessBase
Indicates that one entity serves as the primary business foundation, core location, or main operational base for another entity.
-
B.
business
Indicates that an entity is engaged in commercial or professional activities, such as providing goods or services for profit.
-
C.
coversMarket
Indicates that one entity operates in, serves, or has business presence within a particular market or geographic/sectoral area.
-
D.
centralBusiness
Indicates that an entity functions as the primary commercial or economic hub (central business area or role) in relation to another entity.
-
E.
frontBusiness
chosen
Indicates that one entity operates as a façade or cover business for another entity, typically concealing the latter’s true activities or identity.
- 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_69d6aa9687448190b28d353b1b6a610e |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797baad408190a53fd6941a750f68 |
completed | April 9, 2026, 12:12 p.m. |
| PD | Predicate disambiguation | batch_69d72e995e008190bbffb314129ed0cd |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:25 p.m.