Triple
T1086310
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Children of Gebelawi |
E24057
|
entity |
| Predicate | hasProtagonistGroup |
P24067
|
FINISHED |
| Object | descendants of Gebelawi |
—
|
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: descendants of Gebelawi | Statement: [Children of Gebelawi, hasProtagonistGroup, descendants of Gebelawi]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistGroup Context triple: [Children of Gebelawi, hasProtagonistGroup, descendants of Gebelawi]
-
A.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
B.
hasAntagonistGroup
Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
-
C.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
D.
protagonistType
Indicates the role or category that the main character (protagonist) of a story or scenario belongs to.
-
E.
hasEnigmaticCharacter
Indicates that something possesses a mysterious, puzzling, or difficult-to-interpret quality or nature.
- 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_69a49404428c819092dcc9632f5f7b8b |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4b963161081908a523c8d63871652 |
completed | March 1, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69a4b7407914819092ed933a7316b450 |
completed | March 1, 2026, 10:01 p.m. |
| PDg | Predicate description generation | batch_69a4b8f1097881908932d7eea4331917 |
completed | March 1, 2026, 10:08 p.m. |
Created at: March 1, 2026, 7:42 p.m.