Triple
T36581042
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mountmellick |
E902394
|
entity |
| Predicate | embroideryCharacteristic |
P64189
|
FINISHED |
| Object | heavily textured stitches |
—
|
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: heavily textured stitches | Statement: [Mountmellick, embroideryCharacteristic, heavily textured stitches]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: embroideryCharacteristic Context triple: [Mountmellick, embroideryCharacteristic, heavily textured stitches]
-
A.
textileFeature
chosen
Indicates a characteristic, property, or notable aspect associated with a textile or fabric.
-
B.
fiberCharacteristic
Indicates a relationship where a specific characteristic or property is attributed to a fiber or fibrous material.
-
C.
spanCharacteristic
Indicates that one entity has a particular measurable or descriptive property that characterizes the extent, duration, or range of another entity or phenomenon.
-
D.
textileType
Indicates the specific kind or category of textile material associated with an entity.
-
E.
stitchQuality
Indicates the degree to which stitching between components is executed accurately, consistently, and without defects.
- 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_69f76e64d8908190868473959a250b94 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c777e924819081a6634f549fe552 |
completed | May 3, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69f7c477a4d481908f52e55b6688f60c |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:11 p.m.