Triple
T6523373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscato d’Asti |
E151241
|
entity |
| Predicate | typicalClosure |
P65693
|
FINISHED |
| Object | cork |
—
|
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: cork | Statement: [Moscato d’Asti, typicalClosure, cork]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalClosure Context triple: [Moscato d’Asti, typicalClosure, cork]
-
A.
closureType
chosen
Indicates the specific manner or condition in which something is closed, completed, or terminated within a process or relationship.
-
B.
closureBy
Indicates that one entity causes, performs, or is responsible for the closing or termination of another entity, event, or process.
-
C.
closure
Indicates that an entity is closed or not accessible/available for use, entry, or interaction.
-
D.
subjectToClosure
Indicates that an entity is liable or scheduled to be closed, discontinued, or shut down under certain conditions or plans.
-
E.
notableClosure
Indicates that an entity is recognized for a significant or noteworthy ending, shutdown, or termination event.
- 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_69c687f522748190b3058405553cdabd |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad970afc81909d3231203eacf413 |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.