Triple
T13082201
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Insecta |
E310235
|
entity |
| Predicate | metamorphosisType |
P107941
|
FINISHED |
| Object | complete 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: complete metamorphosis | Statement: [Insecta, metamorphosisType, complete metamorphosis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: metamorphosisType Context triple: [Insecta, metamorphosisType, complete metamorphosis]
-
A.
speciesType
Indicates the specific biological species category to which an entity belongs.
-
B.
metamorphismRelatedTo
Indicates a relationship where one geological feature, process, or condition is connected to or influences the metamorphic transformation of rocks or minerals.
-
C.
wasTransformedBy
Indicates that an entity has undergone a change of state, form, or condition as the result of an action, process, or agent.
-
D.
adaptationType
Indicates the specific kind or category of adaptation that relates one entity to another or to a particular context.
-
E.
oreType
Indicates the specific kind or classification of ore associated with an 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_69d806a733548190989cfd4ce981ca33 |
completed | April 9, 2026, 8:05 p.m. |
| NER | Named-entity recognition | batch_69d9811add9881908a92186dab5b6d48 |
completed | April 10, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69d9803f6c508190bfadfbc2d00c2c64 |
completed | April 10, 2026, 10:57 p.m. |
| PDg | Predicate description generation | batch_69d98114a6508190b1e8e018bb5a068c |
completed | April 10, 2026, 11 p.m. |
Created at: April 9, 2026, 9:01 p.m.