Triple
T36702787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brachyrhaphis roseni |
E906273
|
entity |
| Predicate | developmentMode |
P194925
|
FINISHED |
| Object | viviparous |
—
|
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: viviparous | Statement: [Brachyrhaphis roseni, developmentMode, viviparous]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developmentMode Context triple: [Brachyrhaphis roseni, developmentMode, viviparous]
-
A.
developmentTime
Indicates the duration or period required for something to be developed or brought from inception to completion.
-
B.
developmentVariant
Indicates that one entity is a variant or alternative form of another in the context of development (e.g., a different developmental version, configuration, or pathway).
-
C.
developmentMethod
Indicates the process, technique, or approach used to create, build, or evolve something.
-
D.
developmentFeature
Indicates that one entity serves as a developmental feature, aspect, or component of another entity within a growth or improvement process.
-
E.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd8e5f7c4c8190ab8e2f2a7bb1bd79 |
completed | May 8, 2026, 7:18 a.m. |
| PD | Predicate disambiguation | batch_69fd8d8a16f08190b9e880901bfa44fe |
completed | May 8, 2026, 7:15 a.m. |
| PDg | Predicate description generation | batch_69fd8e5e9ca48190890a2caddc1f9f5c |
completed | May 8, 2026, 7:18 a.m. |
Created at: May 3, 2026, 4:12 p.m.