Triple
T31481428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bushmills Causeway Collection |
E803153
|
entity |
| Predicate | hasLabelInformation |
P176317
|
FINISHED |
| Object | vintage year on some expressions |
—
|
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: vintage year on some expressions | Statement: [Bushmills Causeway Collection, hasLabelInformation, vintage year on some expressions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLabelInformation Context triple: [Bushmills Causeway Collection, hasLabelInformation, vintage year on some expressions]
-
A.
hasLabel
Indicates that an entity is associated with a specific textual label or name used to identify or describe it.
-
B.
hasLabelSet
Indicates that an entity is associated with a specific collection or set of labels.
-
C.
isLabeledOn
Indicates that a label, tag, or identifying text is physically or virtually attached to or displayed on an entity.
-
D.
hasLabelHistory
Indicates that an entity is associated with a record of its past labels, including changes over time.
-
E.
hasKeyInformation
chosen
Indicates that an entity possesses or contains essential or critical information relevant to another entity, context, or task.
- 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_69f348c9477c8190bc0a21f6d482d2fc |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 30, 2026, 9:32 p.m.