Triple
T31463987
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mexican Sign Language |
E802674
|
entity |
| Predicate | usesRoleShift |
P179252
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Mexican Sign Language, usesRoleShift, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRoleShift Context triple: [Mexican Sign Language, usesRoleShift, yes]
-
A.
usesRoleTypes
Indicates that an entity employs or is associated with specific role classifications or role types within a given context.
-
B.
exportRole
Indicates that an entity functions in a capacity or role specifically related to exporting goods, services, or data.
-
C.
interchangeRole
Indicates that two entities exchange or swap their roles or functional positions with each other.
-
D.
covertRole
Indicates that an entity holds or performs a hidden, secret, or undercover role in relation to another entity or context.
-
E.
roleReplacedOn
Indicates that one role has been substituted or taken over by another role at a specific point in time.
- 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_69f348c84c1c81908739f100ecf7394e |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7201e241c819092d56a7bb99dc94d |
completed | May 3, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
| PDg | Predicate description generation | batch_69f71f8df5d48190944fbfbd9d573868 |
completed | May 3, 2026, 10:12 a.m. |
Created at: April 30, 2026, 9:22 p.m.