Triple
T10724344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mishma |
E252899
|
entity |
| Predicate | hasNoRecorded |
P88306
|
FINISHED |
| Object | death details in the Bible |
—
|
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: death details in the Bible | Statement: [Mishma, hasNoRecorded, death details in the Bible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNoRecorded Context triple: [Mishma, hasNoRecorded, death details in the Bible]
-
A.
hasNoOfficialRecordIn
chosen
Indicates that an entity lacks any recognized or formally documented record within a specified system, registry, or authority.
-
B.
hasRecordingWith
Indicates that one entity is associated with or includes a particular recording as part of its content or representation.
-
C.
hasNotableRecordingBy
Indicates that an entity (such as a work or composition) has a well-known or significant recording created or performed by a specified agent (such as an artist, ensemble, or label).
-
D.
neverCapturedBy
Indicates that one entity has never been apprehended, seized, or taken into custody by another entity at any point in time.
-
E.
hadNo
Indicates that one entity completely lacked or did not possess another entity, attribute, or relationship.
- 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_69d6aa5d8be481909a43218b2bfdbe95 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d70d46234081908e147638d0cb7e22 |
completed | April 9, 2026, 2:21 a.m. |
| PD | Predicate disambiguation | batch_69d6f30455888190b77f476b8418eaee |
completed | April 9, 2026, 12:29 a.m. |
Created at: April 8, 2026, 9:14 p.m.