Triple
T6111279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wykeham Professor of Physics at the University of Oxford |
E136244
|
entity |
| Predicate | holderConducts |
P68218
|
FINISHED |
| Object | research in physics |
—
|
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: research in physics | Statement: [Wykeham Professor of Physics at the University of Oxford, holderConducts, research in physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: holderConducts Context triple: [Wykeham Professor of Physics at the University of Oxford, holderConducts, research in physics]
-
A.
holderIs
Indicates that one entity serves as the holder, possessor, or container of another entity.
-
B.
holderMayBe
Indicates that a particular entity is allowed or permitted to serve as the holder or possessor of another entity.
-
C.
holderMustBe
Indicates that a specified entity is required to be the holder or possessor of another entity or resource.
-
D.
holdsIn
Indicates that a relationship, condition, or event is valid or occurs within a specified time interval or temporal context.
-
E.
heldAs
Indicates that one entity is kept, maintained, or regarded in a particular state, role, or condition by another entity.
- F. None of above. chosen
Provenance (4 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05bbbbea88190b889a7c30af1d71a |
completed | March 22, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.