Triple
T20057004
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lunéville embroidery |
E499363
|
entity |
| Predicate | beadApplicationMethod |
P859
|
FINISHED |
| Object | beads pre-strung on thread |
—
|
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: beads pre-strung on thread | Statement: [Lunéville embroidery, beadApplicationMethod, beads pre-strung on thread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beadApplicationMethod Context triple: [Lunéville embroidery, beadApplicationMethod, beads pre-strung on thread]
-
A.
appliedAs
Indicates that one entity submitted itself or was put forward for consideration in a particular role, position, or context relative to another entity.
-
B.
appliesVia
Indicates that an action, rule, or effect is carried out, implemented, or achieved through a specified method, medium, or mechanism.
-
C.
appliedBy
Indicates that an action, process, or treatment is carried out or executed by a particular agent or entity.
-
D.
method
chosen
Indicates the technique, procedure, or process used by an entity to perform an action or achieve a result.
-
E.
applicatorType
Indicates the specific kind or method of applicator used to apply a substance or product in the described relationship.
- 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e663337d0c8190b82422802396cd67 |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.