Triple
T9072973
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biswamoyopterus |
E217412
|
entity |
| Predicate | observationNote |
P86800
|
FINISHED |
| Object | rarely observed in the wild |
—
|
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: rarely observed in the wild | Statement: [Biswamoyopterus, observationNote, rarely observed in the wild]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: observationNote Context triple: [Biswamoyopterus, observationNote, rarely observed in the wild]
-
A.
observation
Indicates that one entity perceives, monitors, or takes note of another entity or phenomenon, typically to gather information about it.
-
B.
observationType
Indicates the specific kind or category of observation being made or recorded in a given context.
-
C.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
-
D.
behaviorObserved
Indicates that a particular behavior or action has been witnessed, recorded, or detected in relation to an entity or context.
-
E.
observedEvent
Indicates that an entity has perceived, detected, or recorded the occurrence of a particular event.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc955ffa04819086be5763133c5067 |
completed | April 1, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69cc65f881248190bfd220bb28a9fb5f |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc668ad3d881908a8a93a6a1d553e4 |
completed | April 1, 2026, 12:27 a.m. |
Created at: March 30, 2026, 7:12 p.m.