Triple
T26988764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brian Heriot |
E679803
|
entity |
| Predicate | adoptedByCharacterFrom |
P91408
|
FINISHED |
| Object | Woodbury |
—
|
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: Woodbury | Statement: [Brian Heriot, adoptedByCharacterFrom, Woodbury]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adoptedByCharacterFrom Context triple: [Brian Heriot, adoptedByCharacterFrom, Woodbury]
-
A.
usedByCharacter
Indicates that something (such as an item, ability, or resource) is utilized or employed by a particular character.
-
B.
adaptationOfCharacterFrom
Indicates that one character is derived, modified, or reinterpreted from an existing character in another work or version.
-
C.
adoptedFrom
chosen
Indicates that an entity has been taken into guardianship, ownership, or use from another source or origin.
-
D.
basedOnCharacterFromWork
Indicates that one entity is derived from, inspired by, or modeled after a character that appears in another creative work.
-
E.
developedByCharacter
Indicates that something (such as an item, technique, or work) was created, designed, or brought into existence by a particular character.
- 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_69eeeb5138ac8190b3c273ddc659a54f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 6:50 a.m.