Triple
T16791047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amphipoda |
E408109
|
entity |
| Predicate | hasAbdominalLimbs |
P124648
|
FINISHED |
| Object | abdominal limbs adapted for swimming or jumping |
—
|
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: abdominal limbs adapted for swimming or jumping | Statement: [Amphipoda, hasAbdominalLimbs, abdominal limbs adapted for swimming or jumping]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAbdominalLimbs Context triple: [Amphipoda, hasAbdominalLimbs, abdominal limbs adapted for swimming or jumping]
-
A.
hasAntennae
Indicates that one entity possesses or is equipped with antennae as a physical feature.
-
B.
hasHindLegsOf
Indicates that one entity possesses or is characterized by the hind legs belonging to or derived from another entity.
-
C.
hasLimbs
Indicates that an entity possesses one or more limbs as physical appendages.
-
D.
hasNumberOfAntennaePairs
Indicates the relationship that specifies how many pairs of antennae an entity possesses.
-
E.
hasPedipalps
Indicates that an organism possesses pedipalps, the paired appendages located near the mouthparts of certain arthropods.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2a5d10c8190a581de79e4f7ccfa |
completed | April 18, 2026, 4:34 p.m. |
| PD | Predicate disambiguation | batch_69e319cf691c819083e39225f5777ef0 |
completed | April 18, 2026, 5:42 a.m. |
| PDg | Predicate description generation | batch_69e326bac94481908c082117553320f8 |
completed | April 18, 2026, 6:37 a.m. |
Created at: April 10, 2026, 5:22 a.m.