Triple
T6668280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rifian |
E151659
|
entity |
| Predicate | lexicalRelation |
P34778
|
FINISHED |
| Object | shares vocabulary with other Northern Berber varieties |
—
|
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: shares vocabulary with other Northern Berber varieties | Statement: [Rifian, lexicalRelation, shares vocabulary with other Northern Berber varieties]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lexicalRelation Context triple: [Rifian, lexicalRelation, shares vocabulary with other Northern Berber varieties]
-
A.
semanticRelation
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
B.
termRelationTo
chosen
Indicates a general relational association between one term and another, without specifying the exact nature of that relationship.
-
C.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
D.
titleRelation
Indicates a relationship where one entity serves as the title, designation, or formal name associated with another entity.
-
E.
datumRelation
Indicates a relationship where one piece of data is connected to, derived from, or otherwise associated with another piece of data.
- 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:02 p.m.