Triple
T28369697
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pentalagus furnessi |
E718590
|
entity |
| Predicate | rangeMapRegion |
P63804
|
FINISHED |
| Object | Ryukyu Islands |
—
|
NE NERFINISHED |
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: Ryukyu Islands | Statement: [Pentalagus furnessi, rangeMapRegion, Ryukyu Islands]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rangeMapRegion Context triple: [Pentalagus furnessi, rangeMapRegion, Ryukyu Islands]
-
A.
mapRegion
Indicates a relationship where a map or mapping system corresponds to, covers, or is associated with a specific geographic or logical region.
-
B.
rangeRegion
chosen
Indicates that one entity defines or corresponds to the spatial or conceptual region over which another entity extends or is applicable.
-
C.
routeRegion
Indicates that a route is located within, passes through, or is associated with a particular geographic region.
-
D.
regionFrom
Indicates that something originates from, is derived from, or is associated with a particular geographic or administrative region.
-
E.
trackRegion
Indicates that an entity is associated with, occurs within, or is relevant to a specific geographic or logical region used for tracking.
- 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_69eff6ed5af48190be4e0adf298223e0 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c5986bc81908bcab5bd97178059 |
completed | May 2, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:58 a.m.