Triple
T20175726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Well dressing |
E492089
|
entity |
| Predicate | hasPreparationTime |
P24075
|
FINISHED |
| Object | several days |
—
|
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: several days | Statement: [Well dressing, hasPreparationTime, several days]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPreparationTime Context triple: [Well dressing, hasPreparationTime, several days]
-
A.
typicalCookingTime
Indicates the usual duration required to cook something under standard or commonly accepted conditions.
-
B.
recommendedPreparation
Indicates that one entity is suggested or advised as a suitable preparation or prerequisite for engaging with another entity.
-
C.
preparationPeriod
chosen
Indicates the time span allocated before an event or action during which necessary preparations are made.
-
D.
preparationPreference
Indicates how an entity prefers something to be prepared, processed, or made ready (e.g., style, method, or conditions of preparation).
-
E.
preparationBegan
Indicates that the initial actions or processes required for something to be carried out or occur have started.
- 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_69da6266c6888190bc1a3ecf24814d34 |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e668eb50a48190af7de53680ca2f5d |
completed | April 20, 2026, 5:56 p.m. |
| PD | Predicate disambiguation | batch_69e55b0c11cc8190836d1eee5945f000 |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:36 p.m.