Triple
T29852531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgard archaea |
E758100
|
entity |
| Predicate | areTypicallyFoundIn |
P133698
|
FINISHED |
| Object | marine sediments |
—
|
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: marine sediments | Statement: [Asgard archaea, areTypicallyFoundIn, marine sediments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areTypicallyFoundIn Context triple: [Asgard archaea, areTypicallyFoundIn, marine sediments]
-
A.
commonlyFoundOn
Indicates that one entity is typically or frequently located on, attached to, or present upon another entity.
-
B.
foundInSpecies
Indicates that something (such as a feature, gene, or characteristic) occurs in, is present in, or is observed within a particular species.
-
C.
inhabitedIn
chosen
Indicates that an entity lives, resides, or has its dwelling within a specified place or location.
-
D.
onlyNaturalHabitatOf
Indicates that a given location is the sole natural habitat where a particular species or organism occurs in the wild.
-
E.
traditionallyFoundIn
Indicates that something is customarily or historically located, used, or present within a particular place, context, or setting.
- 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_69f2245a82cc8190a387e7d0118d710b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67648f35c8190ab466e413b6dbcb5 |
completed | May 2, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:44 p.m.