Triple
T35967346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sīrat ʿAntar |
E1040180
|
entity |
| Predicate | featuresLoveStoryBetween |
P154818
|
FINISHED |
| Object | Antarah ibn Shaddad |
E313232
|
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: Antarah ibn Shaddad | Statement: [Sīrat ʿAntar, featuresLoveStoryBetween, Antarah ibn Shaddad]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuresLoveStoryBetween Context triple: [Sīrat ʿAntar, featuresLoveStoryBetween, Antarah ibn Shaddad]
-
A.
loveInterestPortrayedBy
Indicates that a character’s romantic interest is depicted or played by a particular actor or performer.
-
B.
hasRomanticPlotline
chosen
Indicates that there is a romantic storyline or relationship development present between the entities.
-
C.
fellInLoveWith
Indicates that one entity developed romantic love or deep affectionate feelings toward another entity.
-
D.
romanticGenreElementIn
Indicates that something functions as a romantic-genre element within a larger work or context.
-
E.
laterLoves
Indicates that one entity comes to love another at a later time than some referenced point or event.
- F. None of above.
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_69f76e26b21081909fd9ffb3aff6c77a |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a397d6680548190a8ba67dfee47839e |
completed | June 22, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:07 p.m.