Triple
T31712519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bigger Fatter Liar |
E809364
|
entity |
| Predicate | hasPlotSimilarityWith |
P94757
|
FINISHED |
| Object | Big Fat Liar |
—
|
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: Big Fat Liar | Statement: [Bigger Fatter Liar, hasPlotSimilarityWith, Big Fat Liar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPlotSimilarityWith Context triple: [Bigger Fatter Liar, hasPlotSimilarityWith, Big Fat Liar]
-
A.
hasSimilarityTo
chosen
Indicates that one entity shares common characteristics, features, or qualities with another entity to a notable degree.
-
B.
hasThematicSimilarityTo
Indicates that two entities share related themes, topics, or conceptual content to a notable degree.
-
C.
namedForSimilarityTo
Indicates that one entity is given its name because of a perceived resemblance or likeness to another entity.
-
D.
hasLexicalSimilarityWith
Indicates that two linguistic items share a significant degree of similarity in form, structure, or wording.
-
E.
hasSimilarAttraction
Indicates that two entities experience or exert a comparable level or type of attraction toward something or each other.
- 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_69f348df4e048190a4a5a9932ada78d6 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fbaebc8f2c8190b94f1b4a3ec92e8c |
completed | May 6, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69fbadf1e6008190a71bbd196ba06844 |
completed | May 6, 2026, 9:09 p.m. |
Created at: April 30, 2026, 11:16 p.m.