Triple
T158618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | King David |
E3231
|
entity |
| Predicate | traditionalAuthorship |
P6838
|
FINISHED |
| Object | many Psalms |
—
|
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: many Psalms | Statement: [King David, traditionalAuthorship, many Psalms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalAuthorship Context triple: [King David, traditionalAuthorship, many Psalms]
-
A.
literaryTradition
Indicates a relationship where a work, practice, or expression belongs to, arises from, or participates in a particular established body of literary customs, styles, or conventions.
-
B.
printedWorkAuthor
Indicates that a person is the creator or writer responsible for the content of a printed work.
-
C.
hasWritingTraditionSince
Indicates that a writing tradition has been present or established for an entity starting from a specified point in time.
-
D.
describedByAuthorAs
Indicates that one entity is characterized, labeled, or portrayed in a particular way by an author.
-
E.
hasAuthor
Indicates that an entity is written or created by a specific author.
- F. None of above. chosen
Provenance (4 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_69a2527757ec819090b8becb2cf1a862 |
completed | Feb. 28, 2026, 2:27 a.m. |
| NER | Named-entity recognition | batch_69a2583169a0819081b658882e5bc452 |
completed | Feb. 28, 2026, 2:51 a.m. |
| PD | Predicate disambiguation | batch_69a25660c2a48190b4174d5e6da3cb9d |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2580b00988190868ee24c0289cf70 |
completed | Feb. 28, 2026, 2:50 a.m. |
Created at: Feb. 28, 2026, 2:31 a.m.