Triple
T6113468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ibrahim Bey |
E136300
|
entity |
| Predicate | nobleTitle |
P914
|
FINISHED |
| Object | Bey |
E415143
|
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: Bey | Statement: [Ibrahim Bey, nobleTitle, Bey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bey Context triple: [Ibrahim Bey, nobleTitle, Bey]
-
A.
Bey
chosen
A Bey was a provincial governor or chieftain in the Ottoman Empire, often wielding significant military and administrative authority.
-
B.
BEY
BEY is the IATA airport code for Beirut–Rafic Hariri International Airport, the main international gateway to Lebanon’s capital city.
-
C.
Bek
Bek is a short or informal given name, typically used as a diminutive of Rebekah.
-
D.
Beyton
Beyton is a small rural village and civil parish in the English county of Suffolk, known for its traditional village green and historic buildings.
-
E.
Bessi
The Bessi were an ancient Thracian tribe known from classical sources for inhabiting mountainous regions and serving as fierce, often rebellious, warriors and priests.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbf2ee4819097af2cce9248bf4e |
completed | March 22, 2026, 9:14 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c12566fb908190bb9c27fe64f618cd |
completed | March 23, 2026, 11:35 a.m. |
Created at: March 22, 2026, 4:14 p.m.