Triple
T17044630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Faifi people |
E413533
|
entity |
| Predicate | ethnonym |
P4709
|
FINISHED |
| Object | Faifi |
E378792
|
NE 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: Faifi | Statement: [Faifi people, ethnonym, Faifi]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Faifi Context triple: [Faifi people, ethnonym, Faifi]
-
A.
Faifi
chosen
Faifi is a modern South Arabian language variety spoken by the Faifi people in the mountainous Jazan region of southwestern Saudi Arabia.
-
B.
Fayiz
Fayiz is a masculine given name of Arabic origin, commonly used as a variant transliteration of the name Fayez.
-
C.
El Mounib
El Mounib is a district in Giza, Egypt, known for serving as a major southern transport hub on the Cairo Metro network.
-
D.
Faisaly
Faisaly is the commonly used short name for Al-Faisaly SC, a professional football club based in Saudi Arabia.
-
E.
Aymen
Aymen is a masculine given name of Arabic origin, commonly considered a variant spelling of Ayman and often associated with meanings like "blessed" or "fortunate."
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3da9c112c81908232dc6908d831cf |
completed | April 18, 2026, 7:25 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a012ed472d48190bc6aed49464dc1ff |
completed | May 11, 2026, 1:20 a.m. |
Created at: April 10, 2026, 5:33 a.m.