Triple
T28327118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cracked Egg (Blue) |
E717439
|
entity |
| Predicate | hasFinishTechnique |
P157582
|
FINISHED |
| Object | mirror-polished |
—
|
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: mirror-polished | Statement: [Cracked Egg (Blue), hasFinishTechnique, mirror-polished]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFinishTechnique Context triple: [Cracked Egg (Blue), hasFinishTechnique, mirror-polished]
-
A.
hasTechnique
Indicates that an entity employs, utilizes, or is associated with a particular method, procedure, or technique.
-
B.
hasTypicalFinish
Indicates that one entity characteristically or commonly concludes, completes, or ends with another entity.
-
C.
hasFinishingMove
Indicates that one entity possesses or is associated with a specific, often decisive or signature, final action or move used to conclude an encounter or event.
-
D.
hasFrameFinish
Indicates that an entity’s frame possesses a specific surface treatment or finish.
-
E.
finishingMethod
chosen
Indicates the technique or process used to complete or finalize an object, task, or work.
- 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_69eff6e9a57c8190a69c2c74b5d72119 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69fd2cf39b0c8190811b8a6fa9410560 |
completed | May 8, 2026, 12:23 a.m. |
| PD | Predicate disambiguation | batch_69fd2ad8dd988190a9899701ba00d917 |
completed | May 8, 2026, 12:14 a.m. |
Created at: April 28, 2026, 12:29 a.m.