Triple
T35309063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Old Custer |
E1019715
|
entity |
| Predicate | creatorOfAuthorCharacter |
P194037
|
FINISHED |
| Object | Wes Anderson |
—
|
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: Wes Anderson | Statement: [Old Custer, creatorOfAuthorCharacter, Wes Anderson]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creatorOfAuthorCharacter Context triple: [Old Custer, creatorOfAuthorCharacter, Wes Anderson]
-
A.
creatorOfCharacter
Indicates that one entity is the originator or author who created or conceived the other entity as a character.
-
B.
creatorOfMainCharacter
Indicates that one entity is the creator or originator of the main character entity in a work or narrative.
-
C.
creatorOfAdaptationCharacterIn
Indicates that a person is the creator of a character that appears in a particular adaptation of a work.
-
D.
hasAuthorAsCharacter
chosen
Indicates that an author appears as a character within a work (such as a book, film, or other narrative).
-
E.
createdByCharacterInUniverse
Indicates that something (such as a work, object, or concept) was created by a specific character within a particular fictional universe.
- 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_69f76de8b4c48190ae504b86185c474c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff70ecc1a481909571b18d56d982b8 |
completed | May 9, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69ff70322a3c8190837840ea42cd3093 |
completed | May 9, 2026, 5:34 p.m. |
Created at: May 3, 2026, 4:03 p.m.