Triple
T26382695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laboulbeniomycetes |
E663180
|
entity |
| Predicate | isMicroscopic |
P151345
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Laboulbeniomycetes, isMicroscopic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMicroscopic Context triple: [Laboulbeniomycetes, isMicroscopic, true]
-
A.
hasMicroscopicDynamics
Indicates that one entity exhibits or is characterized by underlying microscopic-level behaviors, processes, or interactions that govern its dynamics.
-
B.
microscopicStructure
Indicates the detailed arrangement and organization of components at a microscopic scale within an entity.
-
C.
miniaturizedIn
Indicates that one entity exists as a smaller-scale or reduced-size version within or relative to another entity.
-
D.
isMicroorganism
chosen
Indicates that an entity is a microscopic living organism, such as a bacterium, virus, fungus, or protozoan.
-
E.
microscopicMacroscopicLink
Indicates a relationship where microscopic-level phenomena or properties are causally or explanatorily connected to macroscopic-level behavior or observations.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f61076a94481909251f4042116768a |
completed | May 2, 2026, 2:55 p.m. |
| PD | Predicate disambiguation | batch_69f5f800fa9c8190aab0962669fde8ac |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 11:19 p.m.