Triple
T24872519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ponyboy Curtis |
E622472
|
entity |
| Predicate | inspiredToWrite |
P63928
|
FINISHED |
| Object | the story of The Outsiders |
—
|
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: the story of The Outsiders | Statement: [Ponyboy Curtis, inspiredToWrite, the story of The Outsiders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inspiredToWrite Context triple: [Ponyboy Curtis, inspiredToWrite, the story of The Outsiders]
-
A.
inspiredAuthor
Indicates that one entity served as a source of creative or intellectual inspiration for an author entity.
-
B.
hasInspired
chosen
Indicates that one entity has served as a source of motivation, creativity, or influence leading to ideas, actions, or works in another entity.
-
C.
literaryAmbition
Indicates that an entity has the desire, intention, or drive to create, achieve, or succeed in the field of literature.
-
D.
inspiredDocument
Indicates that one entity (often a work, idea, or person) served as the creative or conceptual inspiration for the creation or content of another document.
-
E.
wrote
Indicates that an entity is the author or creator of a written work involving 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f44a417a58819081777e18dda149fd |
completed | May 1, 2026, 6:37 a.m. |
| PD | Predicate disambiguation | batch_69f442b8479c8190a7c8e416ac9e28a0 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 5:23 a.m.