Triple
T22986514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchor |
E571919
|
entity |
| Predicate | commonUsers |
P150506
|
FINISHED |
| Object | embroidery enthusiasts |
—
|
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: embroidery enthusiasts | Statement: [Anchor, commonUsers, embroidery enthusiasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonUsers Context triple: [Anchor, commonUsers, embroidery enthusiasts]
-
A.
traditionalUsers
Indicates that the associated users adhere to long-established or customary practices, methods, or preferences in the given context.
-
B.
otherUsers
Indicates a relationship where one or more users are distinguished as being different from a given primary or reference user.
-
C.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
D.
commonApplication
Indicates that multiple entities share or participate in the same application, process, or usage context.
-
E.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
- 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_69e245b535808190adef8a9df3c584db |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1829a96b8819082e0c6d7fb5d018f |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.