Triple
T5643971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charley Brewster |
E124337
|
entity |
| Predicate | discoversThat |
P19729
|
FINISHED |
| Object | Jerry Dandrige is a vampire |
—
|
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: Jerry Dandrige is a vampire | Statement: [Charley Brewster, discoversThat, Jerry Dandrige is a vampire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: discoversThat Context triple: [Charley Brewster, discoversThat, Jerry Dandrige is a vampire]
-
A.
discoveredAs
Indicates that one entity was first identified, found, or recognized in the role or form specified by another entity.
-
B.
discoveriesInclude
Indicates that one entity’s set of discoveries contains or encompasses the other entity as a discovered item.
-
C.
discovery
chosen
Indicates the event or process by which one entity finds, uncovers, or identifies something previously unknown or unrecognized.
-
D.
discoveredWith
Indicates that one entity was found, detected, or identified using another entity as the means, tool, method, or accompanying context of discovery.
-
E.
discoveredFeature
Indicates that an entity has identified or uncovered a previously unknown or unrecognized feature of another entity or object.
- 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_69c00824643c81909ffdb888a2d35189 |
completed | March 22, 2026, 3:17 p.m. |
| NER | Named-entity recognition | batch_69c022a7cd9c819087f86f60e8b65fc3 |
completed | March 22, 2026, 5:11 p.m. |
| PD | Predicate disambiguation | batch_69c01b2168508190b64b355cf50034ad |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:41 p.m.