Triple
T23710326
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hebrews 7:2 |
E585841
|
entity |
| Predicate | interpretsNameAs |
P82538
|
FINISHED |
| Object | king of peace |
—
|
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: king of peace | Statement: [Hebrews 7:2, interpretsNameAs, king of peace]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interpretsNameAs Context triple: [Hebrews 7:2, interpretsNameAs, king of peace]
-
A.
interpretedAs
Indicates that something is understood, perceived, or taken to mean something else, often based on context or subjective judgment.
-
B.
namedAs
Indicates that one entity is given, known by, or referred to using the name of another entity.
-
C.
isInterpretedBy
Indicates that something (such as data, a work, or a signal) is given meaning, understanding, or explanation by a particular agent or process.
-
D.
importName
Indicates that one entity brings another entity into a scope, module, or context under a specific name used for reference.
-
E.
introducedAsNameIn
chosen
Indicates that an entity is presented or referred to by a particular name within a specified context or source.
- 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_69e24905f77881908194d645676acd60 |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b776d21c8190af48958e1b14aa4c |
completed | April 29, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69f155e4b1148190836ede4741dcb888 |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 6:53 p.m.