Triple
T3884592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kac ring model |
E92908
|
entity |
| Predicate | hasMicroscopicDynamics |
P51619
|
FINISHED |
| Object | time-reversible |
—
|
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: time-reversible | Statement: [Kac ring model, hasMicroscopicDynamics, time-reversible]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMicroscopicDynamics Context triple: [Kac ring model, hasMicroscopicDynamics, time-reversible]
-
A.
hasMIC
Indicates that an entity has a specified Minimum Inhibitory Concentration (MIC) value in relation to an antimicrobial agent.
-
B.
hasMicroplate
Indicates that an entity possesses or is associated with a specific microplate.
-
C.
isMICFor
Indicates that one entity represents the minimum inhibitory concentration (MIC) value determined for another entity, typically a microorganism or drug.
-
D.
hasMicrocontroller
Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
-
E.
hasPhysicalNature
Indicates that one entity possesses or exhibits a specific physical form, composition, or material nature in relation to another.
- 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_69aed9697de0819087c2559295ff3d12 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeec92cc548190b88b899299e5ccdc |
completed | March 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69aee759609c8190985e96ec6d96dedd |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee80858a481909961a33fb50ff8d1 |
completed | March 9, 2026, 3:32 p.m. |
Created at: March 9, 2026, 3:20 p.m.