Triple
T26589652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Makira moorhen |
E667314
|
entity |
| Predicate | occurrenceStatus |
P65652
|
FINISHED |
| Object | possibly extant |
—
|
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: possibly extant | Statement: [Makira moorhen, occurrenceStatus, possibly extant]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occurrenceStatus Context triple: [Makira moorhen, occurrenceStatus, possibly extant]
-
A.
occurrence
Indicates that an event, state, or condition takes place or happens at a particular time or in a particular context.
-
B.
observationalStatus
Indicates the current state or condition of an observation, such as whether it has been made, recorded, verified, or remains pending.
-
C.
continuityStatus
Indicates the state of whether something continues without interruption or has been broken, paused, or reset over time.
-
D.
extantStatus
chosen
Indicates the current existence state of an entity, such as whether it is still present, active, or has ceased to exist.
-
E.
organizationalStatus
Indicates the current state or condition of an organization within a defined context, such as its operational, legal, or membership status.
- 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_69ee9cfc385081909ac9ae178030a06e |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:07 a.m.