Triple
T15017221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bull El |
E377986
|
entity |
| Predicate | emphasizesStatus |
P27548
|
FINISHED |
| Object | supreme god |
—
|
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: supreme god | Statement: [Bull El, emphasizesStatus, supreme god]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: emphasizesStatus Context triple: [Bull El, emphasizesStatus, supreme god]
-
A.
hasEmphasis
Indicates that one element is given special stress, importance, or prominence relative to others.
-
B.
positionEmphasized
Indicates that a particular position, stance, or role is given special prominence or stress relative to others.
-
C.
normativelyEmphasizes
Indicates that one entity highlights, prioritizes, or stresses another entity as a standard, value, or principle that ought to be followed or given special importance.
-
D.
strengthenedStatusOf
chosen
Indicates that the status, condition, or standing of one entity has been made stronger or more robust in relation to another entity or context.
-
E.
impliesStatus
Indicates that one condition, fact, or state logically leads to or determines another status or outcome.
- 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_69d85cd3a3c881908c71fc424d459c17 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded7633fcc8190b2231f43252bc46f |
completed | April 15, 2026, 12:10 a.m. |
| PD | Predicate disambiguation | batch_69de9a67cbc481909c19c2de57de4eb7 |
completed | April 14, 2026, 7:50 p.m. |
Created at: April 10, 2026, 2:55 a.m.