Triple
T8524372
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Skokholm Island |
E201773
|
entity |
| Predicate | birdObservatoryStatus |
P83142
|
FINISHED |
| Object | re‑established 2014 |
—
|
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: re‑established 2014 | Statement: [Skokholm Island, birdObservatoryStatus, re‑established 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: birdObservatoryStatus Context triple: [Skokholm Island, birdObservatoryStatus, re‑established 2014]
-
A.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
-
B.
hasBirdColony
Indicates that one entity hosts or contains a colony of birds associated with it.
-
C.
sightingState
Indicates the current status or condition of a reported sighting within its tracking or verification process.
-
D.
majorBirdGroups
Indicates that the subject entity represents a major taxonomic or evolutionary grouping within birds that includes the object entity as a member or component.
-
E.
hasBirdSpecies
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe644c4648190a14dcaeaa90d72c7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe30d453481908f897ed2b06e7534 |
completed | March 31, 2026, 3:06 p.m. |
Created at: March 30, 2026, 6:16 p.m.