Triple
T1198743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atelopus |
E25727
|
entity |
| Predicate | lifecycle |
P12444
|
FINISHED |
| Object | amphibian metamorphosis |
—
|
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: amphibian metamorphosis | Statement: [Atelopus, lifecycle, amphibian metamorphosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifecycle Context triple: [Atelopus, lifecycle, amphibian metamorphosis]
-
A.
lifeCycle
chosen
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
B.
lifespan
Indicates the duration of time between an entity’s birth (or creation) and its death (or end).
-
C.
designLifetime
Indicates the intended duration or operational period for which something is designed to function as specified.
-
D.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
E.
isForLife
Indicates that something is intended to last or remain valid for the entire duration of a person’s or entity’s 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9c013c8190822d44d465d60fdb |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.