Triple
T32208333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Romani people |
E822731
|
entity |
| Predicate | traditionallyPracticed |
P59382
|
FINISHED |
| Object | nomadism |
—
|
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: nomadism | Statement: [Romani people, traditionallyPracticed, nomadism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionallyPracticed Context triple: [Romani people, traditionallyPracticed, nomadism]
-
A.
practicedTradition
chosen
Indicates that an entity engages in or carries out a particular tradition as a customary or repeated practice.
-
B.
establishedTradition
Indicates that something has become a customary, long-standing practice or convention that is regularly followed within a group, culture, or context.
-
C.
typicalPractice
Indicates that an action, behavior, or method is commonly or customarily done in a given context or by a given group.
-
D.
practicedMedicineOfTradition
Indicates that an entity engaged in the medical practices or healing methods associated with a particular cultural or traditional system.
-
E.
mainTradition
Indicates that one entity represents the primary or dominant tradition associated with another entity.
- 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_69f3490a3bec819097bc58d4731b9d08 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fe9dfaa2d08190b2084f63f842eb6b |
completed | May 9, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69fe9bba947c81908b0b2b92a4d19b37 |
completed | May 9, 2026, 2:28 a.m. |
Created at: May 1, 2026, 12:37 a.m.