Triple
T21208924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John the Baptist |
E522667
|
entity |
| Predicate | nameInIslam |
P29994
|
FINISHED |
| Object | Yahya |
—
|
NE NERFINISHED |
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: Yahya | Statement: [John the Baptist, nameInIslam, Yahya]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Yahya Context triple: [John the Baptist, nameInIslam, Yahya]
-
A.
Yahya
chosen
Yahya is the Islamic prophet identified with John the Baptist, revered for his piety, asceticism, and role in heralding the coming of Prophet Isa (Jesus).
-
B.
Omar
Omar is a municipality located in the province of Sulu in the Philippines.
-
C.
Omar
Omar is a critically acclaimed Palestinian thriller film directed by Hany Abu-Assad that explores love, betrayal, and resistance under Israeli occupation.
-
D.
Omar
Omar is a minor biblical figure listed in the Book of Genesis as one of the descendants of Esau.
-
E.
Omar
Omar is a masculine given name of Arabic origin meaning "flourishing" or "long-lived," borne by numerous historical and contemporary figures worldwide.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e73436eb4c819082e05caf1ba52672 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:26 p.m.