Triple
T36786249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lesser YHWH |
E908919
|
entity |
| Predicate | refersToBeingType |
P94111
|
FINISHED |
| Object | angelic figure |
—
|
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: angelic figure | Statement: [Lesser YHWH, refersToBeingType, angelic figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refersToBeingType Context triple: [Lesser YHWH, refersToBeingType, angelic figure]
-
A.
possibleTypeOfReferent
Indicates that something could be a potential or candidate type or category to which a given referent may belong, without asserting that it definitively is that type.
-
B.
refersToInhabitantsOfType
Indicates that something is referring specifically to inhabitants belonging to a particular type or category.
-
C.
referenceType
chosen
Indicates the specific kind or category of reference relationship that one entity has to another.
-
D.
canBeTypeOf
Indicates that one entity is capable of serving as, or being classified as, a particular type or category of another entity.
-
E.
hasTypeOfReference
Indicates that one entity uses or is associated with a particular kind or category of reference (such as a citation, pointer, or referential link) to another entity.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fec25f0fc48190b87ab1f9cd1eb0de |
completed | May 9, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69fec079a770819098df7cc3049df954 |
completed | May 9, 2026, 5:04 a.m. |
Created at: May 3, 2026, 4:12 p.m.