Triple
T25431982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holbrook Working Professor of Price Theory |
E637281
|
entity |
| Predicate | typicalResearchAreas |
P934
|
FINISHED |
| Object | price formation |
—
|
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: price formation | Statement: [Holbrook Working Professor of Price Theory, typicalResearchAreas, price formation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalResearchAreas Context triple: [Holbrook Working Professor of Price Theory, typicalResearchAreas, price formation]
-
A.
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.
-
B.
isInResearchArea
Indicates that one entity falls within, or is relevant to, the specified research area of another entity.
-
C.
regionOfAcademicInterest
Indicates that an entity has a particular academic field or subject area as its focus of interest or study.
-
D.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
E.
regionOfStudy
Indicates the academic or research area that is the focus of someone’s study or investigation.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
Created at: April 21, 2026, 1:58 p.m.