Triple
T28859613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | three-domain system of Carl Woese |
E728822
|
entity |
| Predicate | usesMarker |
P2130
|
FINISHED |
| Object | small subunit ribosomal RNA |
—
|
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: small subunit ribosomal RNA | Statement: [three-domain system of Carl Woese, usesMarker, small subunit ribosomal RNA]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesMarker Context triple: [three-domain system of Carl Woese, usesMarker, small subunit ribosomal RNA]
-
A.
hasMarker
chosen
Indicates that one entity possesses, is associated with, or is identified by a specific marker.
-
B.
usedMark
Indicates that one entity has employed or applied a particular mark, symbol, or indicator in some context or action.
-
C.
usedToMark
Indicates that one entity serves as a marker, label, or indicator for another entity.
-
D.
usesIndicator
Indicates that one entity employs or relies on another entity as an indicator, signal, or metric for assessment, decision-making, or interpretation.
-
E.
marker
Indicates a relationship where one entity serves as a sign, label, or indicator that identifies, distinguishes, or signals a property or status of another entity.
- 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 6:46 a.m.