Triple
T16187677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ceinture fléchée |
E392849
|
entity |
| Predicate | stillPracticedAs |
P122081
|
FINISHED |
| Object | heritage craft |
—
|
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: heritage craft | Statement: [ceinture fléchée, stillPracticedAs, heritage craft]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stillPracticedAs Context triple: [ceinture fléchée, stillPracticedAs, heritage craft]
-
A.
stillPracticedIn
Indicates that a tradition, custom, or practice continues to be actively carried out or observed in a specified place or context.
-
B.
isPracticedBy
Indicates that an activity, skill, or discipline is regularly performed or carried out by a particular entity.
-
C.
isPracticedAt
Indicates that an activity, skill, or discipline is regularly performed or carried out at a particular location or context.
-
D.
practicedWith
Indicates that one entity engaged in practice or training together with another entity.
-
E.
practicedUnder
Indicates that one entity gained experience or training while working under the guidance, supervision, or mentorship of another entity.
- 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_69d87f1e49ac8190a311b54d32990576 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e220630db481908a0c7f7170f20c5f |
completed | April 17, 2026, 11:58 a.m. |
| PD | Predicate disambiguation | batch_69e219e11f6081909106b1240a17fd37 |
completed | April 17, 2026, 11:30 a.m. |
| PDg | Predicate description generation | batch_69e21e55a2388190b29a045a8c608ba4 |
completed | April 17, 2026, 11:49 a.m. |
Created at: April 10, 2026, 5:02 a.m.