Triple
T27328847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Lake |
E689734
|
entity |
| Predicate | believedHimselfToBe |
P57220
|
FINISHED |
| Object | The Doctor |
—
|
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: The Doctor | Statement: [Jackson Lake, believedHimselfToBe, The Doctor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: believedHimselfToBe Context triple: [Jackson Lake, believedHimselfToBe, The Doctor]
-
A.
believedBySomeToBe
Indicates that at least some people hold the belief that one entity has a particular property, status, or relationship to another entity.
-
B.
believedToHave
Indicates that one entity is thought or assumed, but not confirmed, to possess or exhibit another entity or property.
-
C.
calledHimself
Indicates that a person referred to or identified himself using a particular name, title, or description.
-
D.
believedTo
chosen
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
E.
wasHeldToBe
Indicates that an authority or decision-maker formally judged or determined something to have a particular status, quality, or legal meaning.
- 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_69ef355d4cb08190ab032c0a2e7d3753 |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f643ed0b7481908cf25f3afec0a61d |
completed | May 2, 2026, 6:35 p.m. |
| PD | Predicate disambiguation | batch_69f641dc8ff48190ab575d855616580c |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:37 a.m.