Triple
T32011035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | We’re Here |
E817401
|
entity |
| Predicate | hasAuthorOfWorkItAppearsIn |
P110113
|
FINISHED |
| Object | Rudyard Kipling |
—
|
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: Rudyard Kipling | Statement: [We’re Here, hasAuthorOfWorkItAppearsIn, Rudyard Kipling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAuthorOfWorkItAppearsIn Context triple: [We’re Here, hasAuthorOfWorkItAppearsIn, Rudyard Kipling]
-
A.
authorOfWorkAppearingIn
chosen
Indicates that one entity is the creator or writer of a work that appears within another work or publication.
-
B.
workAppearedInAuthor
Indicates that a particular work by an author appeared in or was included within another creator’s authored work (e.g., as a contribution, feature, or inclusion).
-
C.
appearsInWorkByAuthorFrom
Indicates that an entity appears in a work that was created by an author originating from a specified place or country.
-
D.
hasAuthorOfSameWorkAs
Indicates that two authors are related by having written or contributed to the same work.
-
E.
workOfAuthorOf
Indicates that one entity is a work (such as a book, article, or artwork) created by the author associated with 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_69f348f9e5d081908cc3f57c4942af52 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 12:15 a.m.