Triple
T4639895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Felix Unger |
E101626
|
entity |
| Predicate | fictionalPersonalityTrait |
P37384
|
FINISHED |
| Object | fastidious |
—
|
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: fastidious | Statement: [Felix Unger, fictionalPersonalityTrait, fastidious]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalPersonalityTrait Context triple: [Felix Unger, fictionalPersonalityTrait, fastidious]
-
A.
associatedCharacterTrait
chosen
Indicates a relationship where a character is linked to, or described by, a particular trait or quality.
-
B.
protagonistCharacteristic
Indicates that a characteristic, trait, or defining quality is attributed to the protagonist in a narrative or scenario.
-
C.
fictionalCharacter
Indicates that one entity is a fictional character that appears within the narrative world of another entity (such as a work, series, or franchise).
-
D.
characterDescription
Indicates that one entity provides a textual description or portrayal of the characteristics, traits, or attributes of another entity.
-
E.
fictionalCharacterFrom
Indicates that a fictional character originates from, or is created within, a particular work, universe, or source.
- 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a8fbd2c8190b593cd46ce8dfe0f |
completed | March 20, 2026, 2:32 p.m. |
| PD | Predicate disambiguation | batch_69bd5234d24c819095c79890b70eff9a |
completed | March 20, 2026, 1:57 p.m. |
Created at: March 20, 2026, 1:14 p.m.