Triple
T31179306
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Stapleton |
E794843
|
entity |
| Predicate | pretendsBerylIs |
P84851
|
FINISHED |
| Object | his wife |
—
|
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: his wife | Statement: [Jack Stapleton, pretendsBerylIs, his wife]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pretendsBerylIs Context triple: [Jack Stapleton, pretendsBerylIs, his wife]
-
A.
pretendsToValue
Indicates that one entity outwardly acts as if it values or cares about another entity or object, while not genuinely holding that value internally.
-
B.
emulates
Indicates that one entity imitates or reproduces the behavior, function, or characteristics of another.
-
C.
pretendsConcernFor
chosen
Indicates that one entity feigns or simulates concern for another entity or situation without genuinely feeling it.
-
D.
pretenderPeriod
Indicates a time span during which an entity falsely claims or is regarded as holding a role, title, or status it does not legitimately possess.
-
E.
disguisedAs
Indicates that one entity is intentionally presenting itself as, or made to appear as, another entity in order to conceal its true identity.
- 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_69f224d675d08190957198068e440422 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:08 p.m.