Triple
T1630193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pacific lamprey |
E35237
|
entity |
| Predicate | hasGillOpenings |
P16673
|
FINISHED |
| Object | seven pairs |
—
|
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: seven pairs | Statement: [Pacific lamprey, hasGillOpenings, seven pairs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGillOpenings Context triple: [Pacific lamprey, hasGillOpenings, seven pairs]
-
A.
hasPharyngealSlits
chosen
Indicates that an organism possesses pharyngeal slits, openings in the pharynx that connect the throat to the external environment or a cavity, typically used for filter-feeding or respiration.
-
B.
hasFissureSystem
Indicates that an entity possesses or is characterized by a system of fissures or cracks.
-
C.
hasBodyCavity
Indicates that an organism possesses an internal body cavity or space within its body structure.
-
D.
hasHingedPlastronOrCarapace
Indicates that an entity possesses a plastron or carapace that is hinged, allowing parts of the shell to move relative to each other.
-
E.
hasSporophyteCharacteristic
Indicates that an entity possesses a characteristic or trait associated with the sporophyte stage of a life cycle.
- F. None of above.
Provenance (3 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a9431af5ac8190893133f1ae490142 |
completed | March 5, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69a907c91c888190b6ed295c1a2e0977 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.