Triple
T29852542
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgard archaea |
E758100
|
entity |
| Predicate | areStudiedUsing |
P49589
|
FINISHED |
| Object | metagenomics |
—
|
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: metagenomics | Statement: [Asgard archaea, areStudiedUsing, metagenomics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: areStudiedUsing Context triple: [Asgard archaea, areStudiedUsing, metagenomics]
-
A.
isStudiedUsing
chosen
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
-
B.
studiedBy
Indicates that a subject (such as a field, topic, or object) is examined, researched, or learned by an agent (such as a person or group).
-
C.
alsoStudied
Indicates that an entity pursued additional studies in another subject, field, or institution besides a primary one.
-
D.
canBeStudiedAs
Indicates that something is suitable or appropriate to be examined, analyzed, or researched as a subject of study.
-
E.
hasBeenStudiedFor
Indicates that an entity has been the subject of research, examination, or analysis for a specified purpose, topic, or application.
- 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.