Triple
T25171012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XTSE |
E630321
|
entity |
| Predicate | hasMICStatus |
P42395
|
FINISHED |
| Object | Active |
—
|
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: Active | Statement: [XTSE, hasMICStatus, Active]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMICStatus Context triple: [XTSE, hasMICStatus, Active]
-
A.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
-
B.
hasOperatingMIC
chosen
Indicates that an entity operates or manages a specific MIC (Market Identifier Code) in a financial or trading context.
-
C.
hasCredit
Indicates that an entity possesses or is assigned a credit, such as financial credit, academic credit, or acknowledgment for a contribution.
-
D.
hasICCStatus
Indicates that an entity holds a particular status or designation related to the International Criminal Court (ICC).
-
E.
mintStatusGranted
Indicates that an entity has been officially authorized or approved to mint (create or issue) something, such as tokens, assets, or items.
- 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_69e75a87c9b88190ab60731902a99750 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 12:20 p.m.