Triple
T10364835
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biography |
E244224
|
entity |
| Predicate | hasEpisodeFormatElement |
P23479
|
FINISHED |
| Object | narrated 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: narrated life story | Statement: [Biography, hasEpisodeFormatElement, narrated life story]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEpisodeFormatElement Context triple: [Biography, hasEpisodeFormatElement, narrated life story]
-
A.
hasEpisodeStructure
Indicates that one entity defines or possesses the episodic organization, sequencing, or structural pattern of another (such as a series, season, or narrative work).
-
B.
hasEpisodeLengthType
Indicates the type or category of duration associated with an episode (e.g., standard length, short, extended).
-
C.
hasFormatElement
chosen
Indicates that one entity includes, is composed of, or is associated with a specific structural or formatting component of its overall format.
-
D.
isEpisodeOfType
Indicates that an episode belongs to or is classified under a specific type or category.
-
E.
hasEpisode
Indicates that something, typically a series or program, includes a specific episode as one of its constituent parts.
- 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_69d381b3e328819094b23b8edcd29b5a |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e964a53c8190b748e80850e96656 |
completed | April 7, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69d4dfa657f481909cc5cc8fec00ad19 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, noon