Triple
T32205530
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | drjashton |
E822657
|
entity |
| Predicate | ownerNotability |
P38430
|
FINISHED |
| Object | prominent American physician |
—
|
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: prominent American physician | Statement: [drjashton, ownerNotability, prominent American physician]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ownerNotability Context triple: [drjashton, ownerNotability, prominent American physician]
-
A.
sharesNotabilityWith
Indicates that two entities are notable or recognized for the same or closely related reason, characteristic, or achievement.
-
B.
notabilityStatus
chosen
Indicates whether and how an entity is recognized as notable or significant within a given context or system.
-
C.
notabilityScope
Indicates the domain, field, or context within which something is considered notable or significant.
-
D.
motherNotability
Indicates that an entity’s mother is notable or has significant recognition or prominence.
-
E.
authorityOnNotes
Indicates that one entity is recognized as an expert or primary source of knowledge regarding the notes associated with another entity.
- 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_69f349093174819086e633c190a51aa8 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 12:36 a.m.