Triple
T34635717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holloway’s Ointment |
E889415
|
entity |
| Predicate | applicationRoute |
P39634
|
FINISHED |
| Object | topical |
—
|
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: topical | Statement: [Holloway’s Ointment, applicationRoute, topical]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: applicationRoute Context triple: [Holloway’s Ointment, applicationRoute, topical]
-
A.
administrationRoute
chosen
Indicates the method or pathway by which a substance or treatment is delivered to a subject or system.
-
B.
applicationInterface
Indicates that one entity serves as an interface or interaction layer through which another entity accesses or uses an application’s functionality.
-
C.
exampleRoute
Indicates a route that serves as a representative or illustrative path among possible routes between locations.
-
D.
applicationLocation
Indicates the place or environment where an application is deployed, used, or made available.
-
E.
applicationComponent
Indicates that one entity functions as a component, module, or part within a larger application or software system represented by another entity.
- 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_69f349d724848190b63ad3407e0006d9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69ff2636e2bc8190bba91eff91431c6e |
completed | May 9, 2026, 12:19 p.m. |
| PD | Predicate disambiguation | batch_69ff25c65be48190868480d94e1c4e89 |
completed | May 9, 2026, 12:17 p.m. |
Created at: May 1, 2026, 2:04 a.m.