Triple
T5858054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iris Chase |
E130203
|
entity |
| Predicate | writesWithinStory |
P1955
|
FINISHED |
| Object | manuscript of her life story |
—
|
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: manuscript of her life story | Statement: [Iris Chase, writesWithinStory, manuscript of her life story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: writesWithinStory Context triple: [Iris Chase, writesWithinStory, manuscript of her life story]
-
A.
wroteIn
Indicates that an entity authored or composed something using a particular language, medium, or writing system.
-
B.
writtenDuring
Indicates that the creation or authorship of something took place within a specified time period or historical event.
-
C.
writingComponent
Indicates that one entity is a written part or element that contributes to the composition or structure of another entity.
-
D.
storyBy
chosen
Indicates that one entity is the creator or author of the story associated with another entity.
-
E.
writtenIn
Indicates that a work (such as a text, program, or document) is expressed or encoded using a particular language or notation.
- 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_69c0084f3bb08190a7720f55f7aa4252 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c044ab0a048190b84be40fb13c0f50 |
completed | March 22, 2026, 7:36 p.m. |
| PD | Predicate disambiguation | batch_69c03345ca0c819081c81148d054fed2 |
completed | March 22, 2026, 6:21 p.m. |
Created at: March 22, 2026, 3:56 p.m.