Triple
T4797970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pilsen |
E106758
|
entity |
| Predicate | pilsnerFirstBrewed |
P24657
|
FINISHED |
| Object | 1842 |
—
|
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: 1842 | Statement: [Pilsen, pilsnerFirstBrewed, 1842]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pilsnerFirstBrewed Context triple: [Pilsen, pilsnerFirstBrewed, 1842]
-
A.
firstInscriptionYear
Indicates the year in which an entity was first inscribed, recorded, or officially entered into a relevant register or list.
-
B.
beerBrewedBy
Indicates that a particular beer is produced or created by a specific brewer, brewery, or brewing entity.
-
C.
firstProducedAt
chosen
Indicates the location or context where something was originally created, manufactured, or brought into existence for the first time.
-
D.
breweryType
Indicates the specific category or classification of a brewery based on its operational or business characteristics.
-
E.
wasFirstBuiltInYear
Indicates that the initial construction of an entity was completed in a specified year.
- 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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6b40c29c8190adab3503f8ba0145 |
completed | March 20, 2026, 3:44 p.m. |
| PD | Predicate disambiguation | batch_69bd622f88188190a51d52ccfad3d2dd |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:22 p.m.