Triple
T18275263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Abbotsbury Swannery |
E437717
|
entity |
| Predicate | managedSpecies |
P68322
|
FINISHED |
| Object | mute swan |
—
|
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: mute swan | Statement: [Abbotsbury Swannery, managedSpecies, mute swan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: managedSpecies Context triple: [Abbotsbury Swannery, managedSpecies, mute swan]
-
A.
managesForSpecies
Indicates that one entity is responsible for managing, overseeing, or administering something on behalf of a particular species.
-
B.
subjectSpeciesStatus
Indicates the conservation or biological status assigned to the subject species (e.g., endangered, native, invasive, protected).
-
C.
conservationFocusSpecies
chosen
Indicates that a conservation effort, program, or context is specifically directed toward or centered on a particular species.
-
D.
introducedSpecies
Indicates that a species has been brought by humans, intentionally or unintentionally, into an environment where it does not naturally occur.
-
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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50051bccc8190832eacdb6945d6b7 |
completed | April 19, 2026, 4:18 p.m. |
| PD | Predicate disambiguation | batch_69e44fd81c788190b08c6be3b07a08c5 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:34 a.m.