Triple
T13545910
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holiday 88 |
E323508
|
entity |
| Predicate | trimName |
P110287
|
FINISHED |
| Object | Holiday |
—
|
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: Holiday | Statement: [Holiday 88, trimName, Holiday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trimName Context triple: [Holiday 88, trimName, Holiday]
-
A.
exportName
Indicates that one entity is exported under a specific name or label in relation to another context or system.
-
B.
trimCharacteristic
Indicates that one entity defines or specifies a trimming-related property or feature of another entity.
-
C.
trimFeatures
Indicates that certain features or attributes of an entity are reduced, removed, or cut down, typically to simplify or optimize it.
-
D.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
E.
reformName
Indicates that an entity has undergone a reform or change resulting in a new name or designation.
- F. None of above. chosen
Provenance (4 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbbb9ee3f081909056dc1a92c40b7a |
completed | April 12, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69dbae13bec4819084c1770638c00ed9 |
completed | April 12, 2026, 2:37 p.m. |
| PDg | Predicate description generation | batch_69dbbb8c77dc8190b7bd803b5e168d23 |
completed | April 12, 2026, 3:34 p.m. |
Created at: April 9, 2026, 9:45 p.m.