Triple
T35765295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Weller Martin |
E1033999
|
entity |
| Predicate | revealsThroughGame |
P107569
|
FINISHED |
| Object | personal frustrations |
—
|
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: personal frustrations | Statement: [Weller Martin, revealsThroughGame, personal frustrations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: revealsThroughGame Context triple: [Weller Martin, revealsThroughGame, personal frustrations]
-
A.
isRevealedTo
Indicates that previously hidden or unknown information becomes known to a specific entity or group.
-
B.
isRevealedIn
Indicates that something becomes known, disclosed, or made apparent within a particular context, medium, or situation.
-
C.
revealsThat
Indicates that one entity discloses, exposes, or makes known some information, fact, or state of affairs about another entity or situation.
-
D.
inningsPlayed
Indicates the number of innings in which an entity (typically a player or team) has participated during a game or season.
-
E.
secretRevealedThrough
chosen
Indicates that a secret becomes known or disclosed by means of a specified channel, method, or intermediary.
- 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_69f76e13edd081909101629aa829c4ad |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a1c740a08190811bce8764914921 |
completed | May 3, 2026, 7:28 p.m. |
| PD | Predicate disambiguation | batch_69f7a070e23881909a233370acb57384 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:06 p.m.