Triple
T35522231
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The First and the Last |
E1026574
|
entity |
| Predicate | preparedForPublicationBy |
P59605
|
FINISHED |
| Object | Henry Hardy |
—
|
NE NERFINISHED |
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: Henry Hardy | Statement: [The First and the Last, preparedForPublicationBy, Henry Hardy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: preparedForPublicationBy Context triple: [The First and the Last, preparedForPublicationBy, Henry Hardy]
-
A.
preparationBy
Indicates that one entity is created, assembled, or made ready through the actions or processes performed by another entity.
-
B.
preparedBefore
Indicates that one entity was prepared or made ready at an earlier time than another entity.
-
C.
preparedFor
chosen
Indicates that one entity has been made ready, equipped, or arranged in anticipation of use by or in connection with another entity.
-
D.
preparedAt
Indicates the time or place at which something was prepared or made ready.
-
E.
preparedUnder
Indicates that something was created, processed, or made while being subject to the authority, supervision, or conditions established by a particular person, organization, or standard.
- 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_69f76dfe78b081908e2b14cb88dd8c00 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79a54aa3c8190b2bb5d790b2d42d4 |
completed | May 3, 2026, 6:56 p.m. |
| PD | Predicate disambiguation | batch_69f7961970408190b669cc556e30a608 |
completed | May 3, 2026, 6:38 p.m. |
Created at: May 3, 2026, 4:04 p.m.