Triple
T2478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka Imperial University |
E46
|
entity |
| Predicate | academicDiscipline |
P3
|
FINISHED |
| Object | 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: physics | Statement: [Osaka Imperial University, academicDiscipline, physics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: academicDiscipline Context triple: [Osaka Imperial University, academicDiscipline, physics]
-
A.
academicAdvisor
Indicates that one entity serves as the academic advisor, providing formal guidance and oversight on academic matters, to another entity.
-
B.
academicDegree
Indicates that an entity holds or has been awarded a specific academic degree.
-
C.
academicStructure
Indicates a hierarchical or organizational relationship within an academic system, such as how programs, departments, courses, or degrees are structured and related to one another.
-
D.
campus
Indicates that an entity is located on, associated with, or taking place within a particular campus.
-
E.
fieldOfWork
chosen
Indicates the professional or academic domain in which an entity is primarily engaged or specializes.
- 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_69a22cde80848190b62c5f556b4d62ba |
completed | Feb. 27, 2026, 11:46 p.m. |
| NER | Named-entity recognition | batch_69a23344daf8819083118bbac5f46568 |
completed | Feb. 28, 2026, 12:13 a.m. |
| PD | Predicate disambiguation | batch_69a232e52e7c81909c072703e28e8c61 |
completed | Feb. 28, 2026, 12:12 a.m. |
Created at: Feb. 27, 2026, 11:48 p.m.