Triple
T16268417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guadalupian Epoch |
E394933
|
entity |
| Predicate | terrestrialFloraIncludes |
P100522
|
FINISHED |
| Object | gymnosperms |
—
|
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: gymnosperms | Statement: [Guadalupian Epoch, terrestrialFloraIncludes, gymnosperms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terrestrialFloraIncludes Context triple: [Guadalupian Epoch, terrestrialFloraIncludes, gymnosperms]
-
A.
isLandPlant
Indicates that an entity is a plant that primarily lives and grows on land rather than in aquatic environments.
-
B.
associatedFlora
Indicates a relationship where specific plants or vegetation are characteristically linked to, occur with, or are commonly found in association with a given entity or environment.
-
C.
containsPlantsWith
chosen
Indicates that one entity includes or holds within it one or more plant entities.
-
D.
hasTerrestrialHabitat
Indicates that an entity lives primarily on land or in a ground-based environment rather than in aquatic or aerial habitats.
-
E.
isSeedPlant
Indicates that an entity is a plant that reproduces via seeds rather than spores or other methods.
- 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_69d87f221d8081909b0b2063e7528ba2 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e245ca5c708190a1e98ab37740c032 |
completed | April 17, 2026, 2:38 p.m. |
| PD | Predicate disambiguation | batch_69e219f259e88190bf49d8408c04178e |
completed | April 17, 2026, 11:30 a.m. |
Created at: April 10, 2026, 5:05 a.m.