Triple
T32762622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadsworth |
E837798
|
entity |
| Predicate | guidesOtherCharacters |
P44698
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wadsworth, guidesOtherCharacters, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: guidesOtherCharacters Context triple: [Wadsworth, guidesOtherCharacters, yes]
-
A.
guidesCharacter
chosen
Indicates that one entity provides direction, advice, or mentorship to another entity (the character) in their actions or development.
-
B.
guidesCharactersToward
Indicates a relationship in which one entity directs, influences, or leads characters toward a particular goal, destination, or outcome.
-
C.
characterInspiration
Indicates that one entity serves as the creative or conceptual inspiration for the development or portrayal of another character.
-
D.
metCharacter
Indicates that one entity has encountered or been introduced to another entity at least once.
-
E.
nonHumanCharacter
Indicates that the character involved in the relation is not a human being (e.g., an animal, creature, AI, or other non-human entity).
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6ce6d659881909ddcec1d2966e020 |
completed | May 3, 2026, 4:26 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1667a48190b42684f6ec22dae9 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:13 a.m.