Triple
T19085668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sharks |
E467141
|
entity |
| Predicate | includePartiallyEndothermicSpecies |
P94810
|
FINISHED |
| Object | lamnid sharks |
—
|
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: lamnid sharks | Statement: [Sharks, includePartiallyEndothermicSpecies, lamnid sharks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includePartiallyEndothermicSpecies Context triple: [Sharks, includePartiallyEndothermicSpecies, lamnid sharks]
-
A.
isEndothermic
Indicates that an organism or system generates and maintains its body temperature internally through metabolic heat production.
-
B.
endothermicLineages
Indicates that the related lineages possess or are associated with endothermy (the ability to regulate and maintain a constant internal body temperature through metabolic heat).
-
C.
partlyConsistsOf
chosen
Indicates that one entity is composed in part, but not entirely, of another entity.
-
D.
involvesParticleTransfer
Indicates that the relationship or action includes the movement or exchange of discrete particles from one entity to another.
-
E.
includesSpecies
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
- 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_69d8dd05ac4c8190b1967d8f97f3fb2f |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e346f57c8190a6299e09a0be9e05 |
completed | April 20, 2026, 8:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9a604308190a3235184f9f2c056 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:04 p.m.