Triple
T35081402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Within the Woods |
E1012446
|
entity |
| Predicate | servedAsPrototypeFor |
P196688
|
FINISHED |
| Object | The Evil Dead |
—
|
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: The Evil Dead | Statement: [Within the Woods, servedAsPrototypeFor, The Evil Dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: servedAsPrototypeFor Context triple: [Within the Woods, servedAsPrototypeFor, The Evil Dead]
-
A.
developedAsPrototypeFor
chosen
Indicates that one entity was created in an initial or experimental form specifically to test or serve as a preliminary version for another entity.
-
B.
progenitorOf
Indicates that one entity is the direct biological or ancestral source (parent or originator) of another entity.
-
C.
hasPrototype
Indicates that an entity is based on, derived from, or exemplified by a specific prototype.
-
D.
isPrototypeOfClassUsedIn
Indicates that one class serves as the prototype or template for another class that is used within a given context or system.
-
E.
inheritedFrom
Indicates that one entity has received or derived something (such as traits, rights, or property) from another entity, typically a predecessor or ancestor.
- 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_69f76dd32c008190853aef6028f60208 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffed8912488190baa05f572e5b1b89 |
completed | May 10, 2026, 2:29 a.m. |
| PD | Predicate disambiguation | batch_69ffed12a76c8190ad85c6ac869c72e9 |
completed | May 10, 2026, 2:27 a.m. |
Created at: May 3, 2026, 4:01 p.m.