Triple
T1211565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bufonidae |
E26010
|
entity |
| Predicate | lifeCycleStage |
P9657
|
FINISHED |
| Object | tadpole larval stage |
—
|
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: tadpole larval stage | Statement: [Bufonidae, lifeCycleStage, tadpole larval stage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: lifeCycleStage Context triple: [Bufonidae, lifeCycleStage, tadpole larval stage]
-
A.
lifeStage
Indicates the specific phase or period in an entity’s development or lifecycle that it is currently in.
-
B.
lifeCycle
Indicates the sequence of stages or phases an entity passes through from its beginning, through development and use, to its end or termination.
-
C.
stageOf
chosen
Indicates that one entity represents a particular phase, step, or developmental period within the progression or lifecycle of another entity.
-
D.
lifeStatus
Indicates the current state of an entity’s existence, such as whether it is alive, dead, or in another defined life condition.
-
E.
stages
Indicates that one entity organizes, presents, or sets up another entity (such as an event, performance, or situation) to take place or be displayed.
- 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_69a4948331fc8190b531ac9bec71c491 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4bde581308190bbe30683bf6c48c3 |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb62a7c08190a79dcb6ff72ac99b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.