Triple
T1328841
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarifit |
E28393
|
entity |
| Predicate | hasSVOOrder |
P27272
|
FINISHED |
| Object | yes (variable word order) |
—
|
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 (variable word order) | Statement: [Tarifit, hasSVOOrder, yes (variable word order)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSVOOrder Context triple: [Tarifit, hasSVOOrder, yes (variable word order)]
-
A.
hasOrder
Indicates that one entity possesses, is associated with, or is characterized by a specific order, sequence, or arrangement relative to others.
-
B.
hasStandingOrders
Indicates that an entity has pre-authorized, recurring instructions or arrangements in place to be executed automatically under specified conditions.
-
C.
hasLayOrder
Indicates that one entity has issued, received, or is subject to a formal lay order associated with another entity.
-
D.
isConsentOrder
Indicates that a given legal or regulatory decision is a consent order, i.e., an order entered by agreement of the involved parties rather than imposed unilaterally.
-
E.
hasTextOrder
Indicates that there is a specified sequence or ordering of text elements relative to one another.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c30c948190afc6342b3dcda948 |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
| PDg | Predicate description generation | batch_69a4c0b1326081909aa6beec0cfe8d6c |
completed | March 1, 2026, 10:41 p.m. |
Created at: March 1, 2026, 7:55 p.m.