Triple
T17619093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maxillopoda |
E429661
|
entity |
| Predicate | hasSubgroupWithFreeSwimmingAdults |
P128305
|
FINISHED |
| Object | copepods |
—
|
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: copepods | Statement: [Maxillopoda, hasSubgroupWithFreeSwimmingAdults, copepods]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSubgroupWithFreeSwimmingAdults Context triple: [Maxillopoda, hasSubgroupWithFreeSwimmingAdults, copepods]
-
A.
containsAquaticMembers
Indicates that a group or collection includes one or more members that live in or are adapted to aquatic environments.
-
B.
haveSubgroups
Indicates that an entity is organized into smaller constituent groups that are part of it.
-
C.
hasNotableSubtribe
Indicates that an entity (typically a larger tribal or ethnic group) includes a particular subtribe that is especially recognized or notable.
-
D.
usesSubgroup
Indicates that one entity employs, incorporates, or operates through a specific subgroup of another entity or system.
-
E.
hasAdultVolunteers
Indicates that an entity is associated with one or more adult individuals who volunteer their time or services for it.
- 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_69d889e37f308190a6aa0a69daff86c7 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e46d3489dc8190a619c58025dbb250 |
completed | April 19, 2026, 5:50 a.m. |
| PD | Predicate disambiguation | batch_69e3cdd7da34819099bc9481c5a79bab |
completed | April 18, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69e3cfaac2b881909e1140339eb1a0dd |
completed | April 18, 2026, 6:38 p.m. |
Created at: April 10, 2026, 5:51 a.m.