Triple
T35922603
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | regent honeyeater |
E1038925
|
entity |
| Predicate | NSWStatus |
P150034
|
FINISHED |
| Object | Critically Endangered |
—
|
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: Critically Endangered | Statement: [regent honeyeater, NSWStatus, Critically Endangered]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: NSWStatus Context triple: [regent honeyeater, NSWStatus, Critically Endangered]
-
A.
legalStatusInNSW
chosen
Indicates the legal status or standing of an entity under the laws and regulations specific to New South Wales (NSW).
-
B.
statusModel
Indicates that an entity is associated with a particular status representation or status-handling model.
-
C.
NROStatus
Indicates the current state or condition of an entity within the NRO (e.g., whether it is active, inactive, pending, or in another defined status).
-
D.
CISStatus
Indicates the compliance or certification status of an entity with respect to CIS (Center for Internet Security) benchmarks or standards.
-
E.
nominalStatus
Indicates that an entity holds a particular title, label, or status in name or designation, without necessarily implying associated functions or actions.
- 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_69f76e2320748190b7f5c4750d0cd0d3 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7ac23d1388190bdf9628b294943bd |
completed | May 3, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f7ab734d848190a84f9b8c3a952b75 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 3, 2026, 4:07 p.m.