Triple
T12777008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anchor Island |
E305402
|
entity |
| Predicate | pestManagement |
P106852
|
FINISHED |
| Object | subject to biosecurity controls |
—
|
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: subject to biosecurity controls | Statement: [Anchor Island, pestManagement, subject to biosecurity controls]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pestManagement Context triple: [Anchor Island, pestManagement, subject to biosecurity controls]
-
A.
plantUse
Indicates that a plant is used for a particular purpose, function, or application.
-
B.
pestResistance
Indicates that an entity has the ability to withstand, deter, or remain unaffected by damage or harm caused by pests.
-
C.
notablePest
Indicates that an entity is recognized as a significant or impactful pest, typically causing notable harm, damage, or nuisance.
-
D.
odorControl
Indicates that one entity reduces, neutralizes, or manages the odor produced by another entity or process.
-
E.
crop
Indicates the action of cutting or trimming part of an object or image, typically to remove unwanted outer areas while keeping a selected region.
- F. None of above. chosen
Provenance (4 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_69d7bdf2b43c819098ae5aa68e61ea58 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96e595e008190b42dff3012d17d66 |
completed | April 10, 2026, 9:40 p.m. |
| PD | Predicate disambiguation | batch_69d9640ba0688190973e4e7ec8d4a8e0 |
completed | April 10, 2026, 8:56 p.m. |
| PDg | Predicate description generation | batch_69d96d87078c819083ea724238992204 |
completed | April 10, 2026, 9:37 p.m. |
Created at: April 9, 2026, 5:29 p.m.