Triple
T26707074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Agreement on the Conservation of Albatrosses and Petrels |
E673310
|
entity |
| Predicate | coversSpeciesType |
P10920
|
FINISHED |
| Object | albatross |
—
|
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: albatross | Statement: [Agreement on the Conservation of Albatrosses and Petrels, coversSpeciesType, albatross]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversSpeciesType Context triple: [Agreement on the Conservation of Albatrosses and Petrels, coversSpeciesType, albatross]
-
A.
typeSpecies
Indicates that a species is the designated type species that defines and anchors the taxonomic concept of a higher-level group (such as a genus).
-
B.
speciesType
Indicates the specific biological species category to which an entity belongs.
-
C.
includesSpecies
chosen
Indicates that one entity contains or encompasses one or more species as part of its composition or scope.
-
D.
featuresSpecies
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
E.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
- 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_69eecda2b49c8190a6c481cfc4c07954 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f67f0488bc819089fbd2d2478158d3 |
completed | May 2, 2026, 10:47 p.m. |
| PD | Predicate disambiguation | batch_69f67e3ed894819094c067c1ef624951 |
completed | May 2, 2026, 10:44 p.m. |
Created at: April 27, 2026, 3:34 a.m.