Triple
T6654576
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The History of Little Jack |
E150907
|
entity |
| Predicate | reflectsInterestOfAuthorIn |
P72119
|
FINISHED |
| Object | virtue |
—
|
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: virtue | Statement: [The History of Little Jack, reflectsInterestOfAuthorIn, virtue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reflectsInterestOfAuthorIn Context triple: [The History of Little Jack, reflectsInterestOfAuthorIn, virtue]
-
A.
selfReferenceOfAuthor
Indicates that an author is making a reference to themselves within a work or context.
-
B.
hasAuthorRelationshipToSubject
Indicates that an entity serves as the author or creator of the specified subject.
-
C.
authorParticipation
Indicates that an author takes part in or contributes to a specific work, project, or publication.
-
D.
hasAuthorRelationship
Indicates a relationship where one entity serves as the author or creator of another entity (such as a work, document, or resource).
-
E.
followsWorkOfAuthor
Indicates that one entity continues, builds upon, or is influenced by the work previously produced by a specified 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9d53848190ac75523c157249c6 |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad071b0081909b96dd4b93414bd1 |
completed | March 27, 2026, 4:15 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 2:01 p.m.