Triple
T13451371
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sefer HaMavet |
E320613
|
entity |
| Predicate | conceptualRelation |
P12753
|
FINISHED |
| Object | divine kingship |
—
|
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: divine kingship | Statement: [Sefer HaMavet, conceptualRelation, divine kingship]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: conceptualRelation Context triple: [Sefer HaMavet, conceptualRelation, divine kingship]
-
A.
semanticRelation
chosen
Indicates a general meaning-based connection between two entities, such as similarity, implication, or conceptual association.
-
B.
subjectRelation
Indicates that one entity stands in a specified relational role or connection to another entity.
-
C.
inceptionRelation
Indicates the originating event, source, or initial cause from which another entity, process, or state begins or comes into existence.
-
D.
valueRelation
Indicates a comparative or associative relationship between the values or magnitudes of two or more entities.
-
E.
symbolicRelation
Indicates a relationship where one entity stands for, represents, or conveys meaning about another through symbols or abstract signs.
- 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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaef973b08190a3d7fe1c2a913cff |
completed | April 12, 2026, 2:40 p.m. |
| PD | Predicate disambiguation | batch_69d9a03ce03481908c61094f0cc0c158 |
completed | April 11, 2026, 1:13 a.m. |
Created at: April 9, 2026, 9:41 p.m.