Triple
T38296655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tasker |
E1032105
|
entity |
| Predicate | isBelievedToReferTo |
P57220
|
FINISHED |
| Object | a person |
—
|
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: a person | Statement: [Tasker, isBelievedToReferTo, a person]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isBelievedToReferTo Context triple: [Tasker, isBelievedToReferTo, a person]
-
A.
refersSpecificallyTo
Indicates that one entity makes an explicit, precise reference to another particular entity, distinguishing it from more general or ambiguous references.
-
B.
alsoRefersTo
Indicates that one term, label, or identifier is used as an alternative designation for the same entity or concept as another.
-
C.
believedTo
chosen
Indicates that one entity holds a belief or conviction about the truth, existence, or properties of another entity or proposition.
-
D.
notablyRefersTo
Indicates that one entity makes a particularly significant or noteworthy reference to another entity, beyond a routine or incidental mention.
-
E.
refersToPerson
Indicates that one entity is making reference to, mentioning, or pointing specifically to a particular person.
- 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_69f76e0f2084819091299d021625c3fe |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fccbd826708190b5fab12c4236299a |
completed | May 7, 2026, 5:28 p.m. |
| PD | Predicate disambiguation | batch_69fcc58838e08190b8fa54aa5c165f2d |
completed | May 7, 2026, 5:02 p.m. |
Created at: May 3, 2026, 4:30 p.m.