Triple
T10105908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Methanopyri |
E216319
|
entity |
| Predicate | domainCharacteristic |
P92453
|
FINISHED |
| Object | lacks membrane-bound nucleus |
—
|
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: lacks membrane-bound nucleus | Statement: [Methanopyri, domainCharacteristic, lacks membrane-bound nucleus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: domainCharacteristic Context triple: [Methanopyri, domainCharacteristic, lacks membrane-bound nucleus]
-
A.
managementCharacteristic
Indicates a defining quality, style, or attribute associated with how something is managed or administered.
-
B.
dataCharacteristic
Indicates that one entity specifies a property, attribute, or feature that characterizes a given piece of data.
-
C.
catalogCharacteristic
Indicates that a catalog has a specific characteristic or attribute associated with it.
-
D.
serviceAreaCharacteristic
Indicates a relationship where a service area is associated with a specific attribute or feature that characterizes it.
-
E.
projectCharacteristics
Indicates the defining features, qualities, or attributes that characterize a particular project.
- 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_69ca83d039f08190b9d10363221c69fb |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cdd0c8a0408190be886ec1013a5208 |
completed | April 2, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69cd4b9b853c8190a2af993ce9b21309 |
completed | April 1, 2026, 4:45 p.m. |
| PDg | Predicate description generation | batch_69cd5150ae98819086c4f822114b4e2c |
completed | April 1, 2026, 5:09 p.m. |
Created at: March 30, 2026, 9:03 p.m.