Triple
T8488904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden life of the Earth |
E200906
|
entity |
| Predicate | sustains |
P3636
|
FINISHED |
| Object | subterranean food webs |
—
|
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: subterranean food webs | Statement: [Hidden life of the Earth, sustains, subterranean food webs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sustains Context triple: [Hidden life of the Earth, sustains, subterranean food webs]
-
A.
endures
Indicates that an entity continues to exist, persist, or remain in a particular state or condition over a period of time, often despite challenges or changes.
-
B.
perpetuates
Indicates that one entity causes a state, condition, or situation involving another entity to continue or persist over time.
-
C.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
D.
underpins
chosen
Indicates that one entity serves as the fundamental basis, support, or justification for another.
-
E.
satisfies
Indicates that one entity meets, fulfills, or complies with the requirements, conditions, or expectations specified by another.
- 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_69ca831d7b148190a6e32c1de43ab13b |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe5581d308190b47d76dd49a36529 |
completed | March 31, 2026, 3:16 p.m. |
| PD | Predicate disambiguation | batch_69cbd107633c8190a36ba50e07876918 |
completed | March 31, 2026, 1:49 p.m. |
Created at: March 30, 2026, 6:13 p.m.