Triple
T27635823
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stella Artois |
E696465
|
entity |
| Predicate | heritageDatingBackTo |
P38042
|
FINISHED |
| Object | 1366 |
—
|
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: 1366 | Statement: [Stella Artois, heritageDatingBackTo, 1366]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heritageDatingBackTo Context triple: [Stella Artois, heritageDatingBackTo, 1366]
-
A.
heritageSince
chosen
Indicates that a heritage status, tradition, or cultural legacy has been in effect or recognized starting from a specific point in time.
-
B.
heritagePrecursor
Indicates that one entity serves as an ancestral or foundational predecessor in the heritage or lineage of another entity.
-
C.
heritageRevealedBy
Indicates that an entity’s heritage or origin becomes known or is disclosed through a specified revealing event, source, or process.
-
D.
heritageReference
Indicates that one entity serves as a cultural, historical, or heritage-related reference or source for another entity.
-
E.
heritageBody
Indicates that an entity is officially recognized, managed, or overseen by a heritage organization or authority.
- 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_69ef5909f3848190805f35b76833e722 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6c49627908190b3553474c7c3072b |
completed | May 3, 2026, 3:44 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f23ae081909a52801266063a3c |
completed | May 3, 2026, 3:41 a.m. |
Created at: April 27, 2026, 2:23 p.m.