Triple
T7226067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rod of Asclepius |
E154780
|
entity |
| Predicate | commonMisuseContext |
P4002
|
FINISHED |
| Object | used interchangeably with caduceus in North America |
—
|
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: used interchangeably with caduceus in North America | Statement: [Rod of Asclepius, commonMisuseContext, used interchangeably with caduceus in North America]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonMisuseContext Context triple: [Rod of Asclepius, commonMisuseContext, used interchangeably with caduceus in North America]
-
A.
misuseCanConstitute
Indicates that improper or incorrect use of something can amount to, or be considered as, a particular offense, violation, or condition.
-
B.
usedOutside
Indicates that something is utilized or applied in a context, location, or situation external to its primary or original setting.
-
C.
misappliedAs
chosen
Indicates that something has been used, interpreted, or assigned in an incorrect, inappropriate, or unintended way.
-
D.
endedUseWith
Indicates that an entity has stopped or terminated its use or association with another entity.
-
E.
allegedUse
Indicates that something is claimed or suspected to have been used, without confirming that the use actually occurred.
- 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_69c68811dd1c8190ac460bb39e64e1f0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6e9de21e081908f30700f6211c5ef |
completed | March 27, 2026, 8:34 p.m. |
| PD | Predicate disambiguation | batch_69c6e761b7fc8190857794d78af1b468 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 2:54 p.m.