Triple
T33694490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sabians |
E863265
|
entity |
| Predicate | identifiedBySomeScholarsAs |
P61935
|
FINISHED |
| Object | Mandaeans |
—
|
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: Mandaeans | Statement: [Sabians, identifiedBySomeScholarsAs, Mandaeans]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifiedBySomeScholarsAs Context triple: [Sabians, identifiedBySomeScholarsAs, Mandaeans]
-
A.
possibleIdentificationProposedByScholars
chosen
Indicates that scholars have proposed a possible identification of one entity with another, without asserting it as certain.
-
B.
questionedByScholars
Indicates that the subject has been critically examined, challenged, or doubted by scholars or academic researchers.
-
C.
scholarlyConsensusOnIdentity
Indicates that there is a prevailing agreement among scholars regarding the identity or identification of a particular entity.
-
D.
identifiedIn
Indicates that an entity is recognized, discovered, or documented within a specified source, context, or location.
-
E.
evaluatedByModernScholarsAs
Indicates that something has been judged or characterized in a particular way by contemporary academic or scholarly experts.
- 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_69f3498723a08190ac034339cc78eade |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7234bcaa48190ac970759d34e254a |
completed | May 3, 2026, 10:28 a.m. |
| PD | Predicate disambiguation | batch_69f72155c48881909bd40b9aa3febd5a |
completed | May 3, 2026, 10:20 a.m. |
Created at: May 1, 2026, 1:43 a.m.