Triple
T3804917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Devonian Period |
E91781
|
entity |
| Predicate | terrestrialLife |
P3591
|
FINISHED |
| Object | early forests |
—
|
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: early forests | Statement: [Devonian Period, terrestrialLife, early forests]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrestrialLife Context triple: [Devonian Period, terrestrialLife, early forests]
-
A.
lifeForm
Indicates that an entity is a living organism or belongs to a category of living organisms.
-
B.
biota
chosen
Indicates the presence or composition of living organisms (flora, fauna, or other life forms) associated with a given entity or environment.
-
C.
terrestrialService
Indicates a service or operation that is provided on or relates specifically to land-based (earthbound) environments, as opposed to aerial, maritime, or space-based contexts.
-
D.
hasLivingSpecies
Indicates that an entity currently contains, supports, or is associated with one or more species that are alive or extant.
-
E.
vegetation
Indicates that an area or object is covered with, contains, or is characterized by plant life.
- 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aee8db8a288190afd1e3b9dcf02e97 |
completed | March 9, 2026, 3:35 p.m. |
| PD | Predicate disambiguation | batch_69aee7461abc8190945716f4b93e1a18 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.