Triple
T4225417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nightingale Island |
E94444
|
entity |
| Predicate | hasMainThreats |
P23662
|
FINISHED |
| Object | introduced species |
—
|
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: introduced species | Statement: [Nightingale Island, hasMainThreats, introduced species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainThreats Context triple: [Nightingale Island, hasMainThreats, introduced species]
-
A.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
B.
primaryThreat
chosen
Indicates that one entity is the main or most significant source of danger, harm, or risk to another entity.
-
C.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
D.
historicalThreat
Indicates that one entity posed a significant threat to another in the past, but is not necessarily a current or ongoing danger.
-
E.
threatToHumans
Indicates that the subject poses or represents a potential danger, harm, or risk to humans.
- 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_69b3453700a08190ae88792e3dc63207 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e4d32d481909df7b18f502945b8 |
completed | March 12, 2026, 11:37 p.m. |
| PD | Predicate disambiguation | batch_69b347f1d7b48190bd8974c03c7dc937 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.