Triple
T17127134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Isopoda |
E415624
|
entity |
| Predicate | hasUropods |
P126206
|
FINISHED |
| Object | pair of uropods at posterior end |
—
|
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: pair of uropods at posterior end | Statement: [Isopoda, hasUropods, pair of uropods at posterior end]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUropods Context triple: [Isopoda, hasUropods, pair of uropods at posterior end]
-
A.
hasOpisthodomos
Indicates that an entity (typically a building or temple) includes or is characterized by having an opisthodomos, i.e., a rear room or back chamber.
-
B.
hasOrganBy
Indicates that one entity possesses or includes another entity as an organ or component part.
-
C.
hasUltras
Indicates that an entity has an associated group of passionate, organized supporters or "ultras" linked to it.
-
D.
hasRohe
Indicates a relationship where something is associated with, belongs to, or is located within a specific region or area (rohe).
-
E.
hasSucker
Indicates that one entity possesses or is equipped with a sucker used for attachment, adhesion, or suction in relation to 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f027a3d081908fc1134b50db3d45 |
completed | April 18, 2026, 8:57 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.