Triple
T9708788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesoarchean Era |
E234966
|
entity |
| Predicate | atmosphericState |
P26038
|
FINISHED |
| Object | largely oxygen-poor atmosphere |
—
|
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: largely oxygen-poor atmosphere | Statement: [Mesoarchean Era, atmosphericState, largely oxygen-poor atmosphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atmosphericState Context triple: [Mesoarchean Era, atmosphericState, largely oxygen-poor atmosphere]
-
A.
hasAtmosphere
Indicates that an astronomical body possesses a surrounding layer of gases held by its gravity.
-
B.
atmosphericStudyType
Indicates the specific kind or category of study being conducted on the atmosphere or atmospheric phenomena.
-
C.
hasGeneralAtmosphere
Indicates that one entity is characterized by or associated with a particular overall mood, tone, or ambient quality provided by another entity.
-
D.
hasAtmosphericFeature
chosen
Indicates that one entity possesses or exhibits a particular feature or characteristic of its atmosphere.
-
E.
hasAtmosphericRecord
Indicates that an entity possesses documented data or measurements related to atmospheric conditions or phenomena.
- 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_69ca84cc78808190a56f3402b7c139a7 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cd9da7c6188190b086f7e411378268 |
completed | April 1, 2026, 10:35 p.m. |
| PD | Predicate disambiguation | batch_69cd03bfeca08190924fca43aaa9c10f |
completed | April 1, 2026, 11:38 a.m. |
Created at: March 30, 2026, 8:19 p.m.