Triple
T31342010
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J. W. Milam |
E799329
|
entity |
| Predicate | confessionPublicationYear |
P36012
|
FINISHED |
| Object | 1956 |
—
|
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: 1956 | Statement: [J. W. Milam, confessionPublicationYear, 1956]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confessionPublicationYear Context triple: [J. W. Milam, confessionPublicationYear, 1956]
-
A.
confessionYear
chosen
Indicates the year in which a confession (such as an admission of guilt, belief, or wrongdoing) took place or was formally recorded.
-
B.
confessionAuthored
Indicates that one entity is the creator or writer of a particular confession made or recorded by another entity.
-
C.
madePublicConfessionAt
Indicates that an entity openly admitted or confessed something in a public setting at a specific time or place.
-
D.
confessionObtainedBy
Indicates that a confession was acquired through a particular method, action, or process.
-
E.
confessionalCounterpartOf
Indicates a relationship where one entity serves as the corresponding or opposite party in a confessional context to another entity (e.g., the person who hears or receives the confession).
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: April 29, 2026, 9:17 p.m.