Triple
T23629564
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Testament of Solomon |
E583568
|
entity |
| Predicate | notCanonicalIn |
P20093
|
FINISHED |
| Object | Jewish Bible |
—
|
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: Jewish Bible | Statement: [Testament of Solomon, notCanonicalIn, Jewish Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notCanonicalIn Context triple: [Testament of Solomon, notCanonicalIn, Jewish Bible]
-
A.
notOfficialIn
Indicates that an entity does not hold an official role, status, or position within a specified organization, group, or jurisdiction.
-
B.
notInCanonOf
chosen
Indicates that something is excluded from, or does not belong to, the officially recognized canon of a given work or universe.
-
C.
notEstablishedBy
Indicates that a given entity, state, or condition does not originate from, is not created by, and is not the result of the specified agent or source.
-
D.
notAbout
Indicates that a given entity, statement, or resource does not concern, reference, or pertain to another specified entity or topic.
-
E.
notStatus
Indicates that an entity does not have, is not in, or does not match a specified status or state.
- 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_69e248fc8d74819091bd5baef2f36f6f |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b1e71cac8190a3e1c04d7a5fffa1 |
completed | April 29, 2026, 7:23 a.m. |
| PD | Predicate disambiguation | batch_69f118d0e0588190a86527a7747c5427 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:46 p.m.