Triple
T2331085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nanoarchaeota |
E44202
|
entity |
| Predicate | cellSize |
P38983
|
FINISHED |
| Object | approximately 400 nanometers or less in diameter |
—
|
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: approximately 400 nanometers or less in diameter | Statement: [Nanoarchaeota, cellSize, approximately 400 nanometers or less in diameter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellSize Context triple: [Nanoarchaeota, cellSize, approximately 400 nanometers or less in diameter]
-
A.
stateSize
Indicates the relative or absolute physical extent or dimensions of a state, such as its area or population size.
-
B.
fieldSize
Indicates the magnitude or dimensions of a field associated with an entity or context.
-
C.
blockSize
Indicates the size or capacity of a discrete block unit within a larger structure or system.
-
D.
characterCellResolution
Indicates a relationship where the visual or logical representation of characters is determined or adjusted at the level of individual cells (e.g., grid units or display slots).
-
E.
grainSize
Indicates the relative coarseness or fineness of the material or particles involved in the relationship.
- 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_69a889132b488190bbb43ad4780ddd92 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abcc30c5e881908c5d526d7e7491d0 |
completed | March 7, 2026, 6:56 a.m. |
| PD | Predicate disambiguation | batch_69abc5926d048190a535e3f23d41de2a |
completed | March 7, 2026, 6:28 a.m. |
| PDg | Predicate description generation | batch_69abcc2fa25c8190858c1c541b914f4c |
completed | March 7, 2026, 6:56 a.m. |
Created at: March 4, 2026, 7:51 p.m.