Triple
T5645431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Baigas |
E124372
|
entity |
| Predicate | practise |
P4721
|
FINISHED |
| Object | endogamy at community level |
—
|
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: endogamy at community level | Statement: [Baigas, practise, endogamy at community level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: practise Context triple: [Baigas, practise, endogamy at community level]
-
A.
practice
chosen
Indicates that an entity regularly performs an activity or skill, typically to improve proficiency or maintain competence.
-
B.
homePractice
Indicates that an activity, skill, or task is being practiced or carried out in a home setting rather than in a formal or external environment.
-
C.
hadPractice
Indicates that an entity engaged in or participated in a practice session or rehearsal.
-
D.
extendedPractice
Indicates that an entity engages in a prolonged or repeated practice or rehearsal of an activity beyond its usual or standard duration.
-
E.
mentionsPractice
Indicates that one entity refers to, discusses, or brings up a particular practice in some form of communication.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022aa650c819088d9046b82fab631 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.