Triple
T31033172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wenlock Epoch |
E790783
|
entity |
| Predicate | reefDevelopment |
P170685
|
FINISHED |
| Object | major expansion of Silurian reef ecosystems |
—
|
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: major expansion of Silurian reef ecosystems | Statement: [Wenlock Epoch, reefDevelopment, major expansion of Silurian reef ecosystems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reefDevelopment Context triple: [Wenlock Epoch, reefDevelopment, major expansion of Silurian reef ecosystems]
-
A.
reefType
Indicates the specific classification or category of reef associated with an entity.
-
B.
reefRepresents
Indicates that a reef serves as a symbol, depiction, or stand-in representation for another entity or concept.
-
C.
reefCommunities
Indicates that entities are associated through the structure, composition, or dynamics of biological communities living on or around a reef.
-
D.
nearReef
Indicates that one entity is located close to or in the vicinity of a reef.
-
E.
reefName
Indicates that a reef is identified by a specific name.
- F. None of above. chosen
Provenance (4 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_69f224c97a788190b5da1ead6038a74e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f694c3e0f881909ea3548ec8ab3eaf |
completed | May 3, 2026, 12:20 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 8:59 p.m.