Triple
T1933764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euryarchaeota |
E41402
|
entity |
| Predicate | characteristicProcess |
P4106
|
FINISHED |
| Object | methane production |
—
|
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: methane production | Statement: [Euryarchaeota, characteristicProcess, methane production]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characteristicProcess Context triple: [Euryarchaeota, characteristicProcess, methane production]
-
A.
characterizedBy
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
-
B.
constructionCharacteristic
Indicates a specific structural or material property that characterizes how something is built or constructed.
-
C.
logisticalCharacteristic
Indicates the logistical properties or constraints associated with an entity, such as how it is stored, transported, handled, or supplied.
-
D.
partOfProcess
chosen
Indicates that one event, step, or action occurs as a component or stage within a larger overall process.
-
E.
trainingCharacteristic
Indicates that an entity has a specific property, feature, or quality related to training (such as method, intensity, or style).
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29b51408190afb2f918814e68c7 |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abafeec6f881909d47acb966683279 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.