Triple
T25508709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stella |
E639313
|
entity |
| Predicate | isAddressedInWorkBy |
P80280
|
FINISHED |
| Object | Sir Philip Sidney |
—
|
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: Sir Philip Sidney | Statement: [Stella, isAddressedInWorkBy, Sir Philip Sidney]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAddressedInWorkBy Context triple: [Stella, isAddressedInWorkBy, Sir Philip Sidney]
-
A.
discussedInWorkOf
chosen
Indicates that a subject is examined, treated, or talked about within a particular work or publication.
-
B.
basedOnWorkAuthorAssociatedWith
Indicates that one entity is derived from or related to a work whose author is associated with another specified entity.
-
C.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
D.
hasReferenceWork
Indicates that one entity is associated with a reference work (such as a dictionary, encyclopedia, or manual) that provides authoritative information about it.
-
E.
isAWorkBy
Indicates that one entity is a creative work that has been produced or authored by 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_69e75dbd09308190b6b5f0afdc12ec6d |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f80844488190bbbaa6bd2e487940 |
completed | May 2, 2026, 1:11 p.m. |
| PD | Predicate disambiguation | batch_69f480789be08190ab252a6de3797200 |
completed | May 1, 2026, 10:29 a.m. |
Created at: April 21, 2026, 2:48 p.m.