Triple
T36251033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | al-Fadl ibn Sahl |
E891802
|
entity |
| Predicate | meaningOfAlias |
P78862
|
FINISHED |
| Object | Possessor of the Two Headships |
—
|
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: Possessor of the Two Headships | Statement: [al-Fadl ibn Sahl, meaningOfAlias, Possessor of the Two Headships]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: meaningOfAlias Context triple: [al-Fadl ibn Sahl, meaningOfAlias, Possessor of the Two Headships]
-
A.
alternativeNameMeaning
chosen
Indicates that one entity expresses the meaning or interpretation of an alternative name used for another entity.
-
B.
lettersMeaning
Indicates that a set of letters or characters represents, signifies, or conveys a particular meaning or message.
-
C.
nickNameMeaning
Indicates that a nickname is associated with a particular meaning, interpretation, or significance.
-
D.
letterMeaning
Indicates that a particular letter conveys a specific meaning, interpretation, or semantic content.
-
E.
notableAliasExplanation
Indicates that an explanation is provided for why a particular alias of an entity is notable or significant.
- F. None of above.
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_69f76e4599108190811532e707d6bc2c |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b5f9a88c819089c3f1e355b45f15 |
completed | May 3, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c44390819084fb5558b354658f |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 3, 2026, 4:09 p.m.