Triple
T28555640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sophie Davis |
E722996
|
entity |
| Predicate | hasNameUsedBy |
P2937
|
FINISHED |
| Object | Sophie Davis School of Biomedical Education |
—
|
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: Sophie Davis School of Biomedical Education | Statement: [Sophie Davis, hasNameUsedBy, Sophie Davis School of Biomedical Education]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameUsedBy Context triple: [Sophie Davis, hasNameUsedBy, Sophie Davis School of Biomedical Education]
-
A.
nameUsedBy
chosen
Indicates that a particular name is employed or referenced by a specific entity.
-
B.
nameUsedBefore
Indicates that a particular name has been used or referenced at an earlier time or in a prior context relative to the current one.
-
C.
nameUsedIn
Indicates that a particular name is employed or referenced within a specified context, work, or usage setting.
-
D.
hasGivenNameUsage
Indicates that an entity is associated with a particular way or context in which its given name is used.
-
E.
hasNameEntityUsage
Indicates that an entity is associated with a particular usage or occurrence of a specific name.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69fd05ba6b2c81909c62b46237d10365 |
completed | May 7, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd03039e48819082b6e12c5453885a |
completed | May 7, 2026, 9:24 p.m. |
Created at: April 28, 2026, 3:45 a.m.