Triple
T4915343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Scott |
E110332
|
entity |
| Predicate | signatureSpeciesFocus |
P7733
|
FINISHED |
| Object | geese and wildfowl |
—
|
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: geese and wildfowl | Statement: [Peter Scott, signatureSpeciesFocus, geese and wildfowl]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: signatureSpeciesFocus Context triple: [Peter Scott, signatureSpeciesFocus, geese and wildfowl]
-
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.
featuresSpecies
chosen
Indicates that something includes, presents, or highlights a particular species as part of its content or composition.
-
C.
speciesType
Indicates the specific biological species category to which an entity belongs.
-
D.
someSpeciesAre
Indicates that at least one member of a specified group or category belongs to, or can be classified as, a particular species.
-
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_69bd44132b94819088522d92beaadc78 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6fa404f881908b4f983983ac7076 |
completed | March 20, 2026, 4:02 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3421588190ab08e92b9558042e |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:29 p.m.