Triple
T8488915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hidden life of the Earth |
E200906
|
entity |
| Predicate | largelyUnseenBecause |
P68420
|
FINISHED |
| Object | occurs below Earth’s surface |
—
|
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: occurs below Earth’s surface | Statement: [Hidden life of the Earth, largelyUnseenBecause, occurs below Earth’s surface]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: largelyUnseenBecause Context triple: [Hidden life of the Earth, largelyUnseenBecause, occurs below Earth’s surface]
-
A.
rarelyVisited
Indicates that an entity is infrequently or seldom visited by others.
-
B.
isLesserKnown
Indicates that one entity is less widely recognized, famous, or familiar than another comparable entity.
-
C.
covered
Indicates that one entity lies over or on top of another entity so as to conceal, protect, or obscure it.
-
D.
hiddenIn
chosen
Indicates that one entity is concealed within, behind, or inside another entity so that it is not readily visible or apparent.
-
E.
notObservedIn
Indicates that a particular entity, event, or property has not been detected, recorded, or seen within a specified context, dataset, or environment.
- 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.