Triple
T30504130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeretes melanopterus |
E776217
|
entity |
| Predicate | hasGlidingMembrane |
P169796
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Aeretes melanopterus, hasGlidingMembrane, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGlidingMembrane Context triple: [Aeretes melanopterus, hasGlidingMembrane, true]
-
A.
hasMesoglea
Indicates that an organism or structure possesses a mesoglea, the gelatinous layer found between tissue layers in certain animals (e.g., cnidarians and ctenophores).
-
B.
hasWingOf
Indicates that one entity possesses or is associated with the wing that belongs to another entity.
-
C.
glidingMechanism
Indicates a mechanism or method by which an entity moves smoothly by gliding, typically with minimal friction or powered motion.
-
D.
hasWingFunction
Indicates that an entity possesses a wing and specifies the functional role or purpose that the wing serves.
-
E.
hasWingIn
Indicates that an entity possesses a wing that is located in or contained within another specified entity or structure.
- 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_69f2249a155c8190b1d512106007e9bb |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f687b1f5e481908b418423c77edbec |
completed | May 2, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:15 p.m.