Triple
T6896222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hahajima |
E159375
|
entity |
| Predicate | hasThreats |
P73999
|
FINISHED |
| Object | invasive 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: invasive species | Statement: [Hahajima, hasThreats, invasive species]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasThreats Context triple: [Hahajima, hasThreats, invasive species]
-
A.
recognizesThreat
Indicates that an entity identifies or acknowledges another entity or situation as a potential danger or source of harm.
-
B.
threatsManaged
Indicates that one entity takes responsibility for identifying, controlling, or mitigating risks or dangers affecting another entity or system.
-
C.
threatenedBy
Indicates that one entity poses a danger or potential harm to another entity.
-
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.
threatStatus
Indicates the level or category of risk or danger posed by one entity to another or to a defined system or environment.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6d95ae3f88190b7f5d440f90ae9f9 |
completed | March 27, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69c6d7b7681481909ec50509b19fcf81 |
completed | March 27, 2026, 7:17 p.m. |
| PDg | Predicate description generation | batch_69c6d8c48ba48190b8d3aa7b8d22816b |
completed | March 27, 2026, 7:21 p.m. |
Created at: March 27, 2026, 2:24 p.m.