Triple
T10569122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Teda people |
E249431
|
entity |
| Predicate | politicalStatusInLibya |
P34171
|
FINISHED |
| Object | ethnic minority in Libya |
—
|
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: ethnic minority in Libya | Statement: [Teda people, politicalStatusInLibya, ethnic minority in Libya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: politicalStatusInLibya Context triple: [Teda people, politicalStatusInLibya, ethnic minority in Libya]
-
A.
statusInLibya
chosen
Indicates the legal, social, or political condition or standing that an entity holds within the context of Libya.
-
B.
recognizedAsLibyaRepresentativeBy
Indicates that an entity is officially acknowledged or accepted as the legitimate representative of Libya by another specified party.
-
C.
importanceInLibya
Indicates the degree to which something holds significance, influence, or priority within the context of Libya.
-
D.
politicalStatusInSyria
Indicates the political role, position, or standing that an entity holds within the context of Syria.
-
E.
claimedLimitByLibya
Indicates that a specified limit, boundary, or extent is asserted or claimed by Libya as its own.
- 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_69d381c8bd708190acf3d275c908251e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d52730fd4481908b3f4eb80ca209f2 |
completed | April 7, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69d51901ff6c819095e7b528170a69dc |
completed | April 7, 2026, 2:47 p.m. |
Created at: April 6, 2026, 12:37 p.m.