Triple
T705714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eugene McDermott |
E14093
|
entity |
| Predicate | hasDomainOfExpertise |
P934
|
FINISHED |
| Object | applied geophysics |
—
|
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: applied geophysics | Statement: [Eugene McDermott, hasDomainOfExpertise, applied geophysics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDomainOfExpertise Context triple: [Eugene McDermott, hasDomainOfExpertise, applied geophysics]
-
A.
hasSpecialty
Indicates that an entity possesses a particular area of expertise, focus, or professional specialization.
-
B.
hasCompetence
Indicates that an entity possesses the ability, skill, or qualification to perform a specific task or function effectively.
-
C.
hasLinguisticDomain
Indicates that something (such as a term, expression, or resource) is associated with or applies within a particular linguistic domain or language context.
-
D.
hasResearchArea
chosen
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
E.
hasSubdiscipline
Indicates that one discipline includes another, more specialized field of study as a subordinate branch.
- 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_69a493494ec48190ae6751683625a9ba |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a58d4c3c8190ad4527d14bca5e6e |
completed | March 1, 2026, 8:46 p.m. |
| PD | Predicate disambiguation | batch_69a4a4edc33881909a978268f6dd5d82 |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.