Triple
T26236262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XTAI |
E656179
|
entity |
| Predicate | hasMICType |
P167078
|
FINISHED |
| Object | operating MIC |
—
|
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: operating MIC | Statement: [XTAI, hasMICType, operating MIC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMICType Context triple: [XTAI, hasMICType, operating MIC]
-
A.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
-
B.
hasOperatingMIC
Indicates that an entity operates or manages a specific MIC (Market Identifier Code) in a financial or trading context.
-
C.
isMICFor
Indicates that one entity represents the minimum inhibitory concentration (MIC) value determined for another entity, typically a microorganism or drug.
-
D.
hasAlternativeMIC
Indicates that an entity is associated with an alternative minimum inhibitory concentration (MIC) value, representing a different measured or applicable MIC than the primary one.
-
E.
hasMP
Indicates that an entity is represented by, or associated with, a specific Member of Parliament (MP).
- F. None of above. chosen
Provenance (4 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_69ee5b4b8b408190993da38c0067cc8d |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f6653ccf648190b65fb1141928e47e |
completed | May 2, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f663ff176c8190aaadb475f75daee4 |
completed | May 2, 2026, 8:52 p.m. |
Created at: April 26, 2026, 9:01 p.m.