Triple
T1286348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Applied Optics |
E27441
|
entity |
| Predicate | disciplineCategory |
P25609
|
FINISHED |
| Object | physics journal |
—
|
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 journal | Statement: [Applied Optics, disciplineCategory, physics journal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: disciplineCategory Context triple: [Applied Optics, disciplineCategory, physics journal]
-
A.
typeDiscipline
chosen
Indicates that an entity is associated with, categorized under, or characterized by a particular discipline or field of study.
-
B.
featuredDiscipline
Indicates that one discipline is highlighted or given special prominence in relation to another entity or context.
-
C.
subDisciplineOf
Indicates that one discipline is a more specialized or narrower field within another, broader discipline.
-
D.
associatedWithDiscipline
Indicates that an entity has a relevant connection or involvement with a particular academic, professional, or thematic discipline.
-
E.
supportsDiscipline
Indicates that one entity provides assistance, resources, or endorsement that helps sustain or advance a particular discipline.
- 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_69a496d4ec448190ad653b2590c46711 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b85eb48190a8b61dc397fa6390 |
completed | March 1, 2026, 10:42 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:51 p.m.