Triple
T18199945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David |
E435754
|
entity |
| Predicate | notableBearerArchetype |
P65465
|
FINISHED |
| Object | biblical king and psalmist |
—
|
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: biblical king and psalmist | Statement: [David, notableBearerArchetype, biblical king and psalmist]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableBearerArchetype Context triple: [David, notableBearerArchetype, biblical king and psalmist]
-
A.
notableBearerDescription
chosen
Indicates that the subject has a notable bearer, with the object providing a textual description of that bearer’s significance or identity.
-
B.
fieldOfNotableBearer
Indicates the professional or activity domain in which a notable bearer of a name, title, or identifier is recognized.
-
C.
notableBearerFullName
Indicates that a full personal name is that of a notable or well-known bearer associated with the referenced entity.
-
D.
notableBearerExecutedBy
Indicates that a notable holder or bearer of something was executed by a specified agent or authority.
-
E.
notableArcRole
Indicates that one entity holds a particularly important or prominent role within a narrative arc or storyline in relation 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_69d8b90dba6481908e119eb9aa4ca0cb |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4e0d610f88190b4f69b1c433ea6b1 |
completed | April 19, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69e4331e92408190ad607ba4956a3897 |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:31 a.m.