Triple
T32453016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mingulay |
E829345
|
entity |
| Predicate | seabirdSpecies |
P29974
|
FINISHED |
| Object | guillemots |
—
|
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: guillemots | Statement: [Mingulay, seabirdSpecies, guillemots]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seabirdSpecies Context triple: [Mingulay, seabirdSpecies, guillemots]
-
A.
birdDiversity
Indicates the variety and richness of different bird species present within a given area, community, or dataset.
-
B.
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.
-
C.
harborsSpecies
Indicates that a location or environment contains, supports, or provides habitat for a particular species.
-
D.
hasBirdSpecies
chosen
Indicates that there exists a relationship in which a subject possesses, contains, or is associated with a particular bird species.
-
E.
migratoryBirdsFrom
Indicates a relationship where the subject is a location or region that serves as the origin from which migratory birds travel or disperse.
- 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_69f3491df9288190afc0b23b1d6e72ce |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c3147ff88190bb4108e817e4eeb1 |
completed | May 3, 2026, 3:37 a.m. |
| PD | Predicate disambiguation | batch_69f6ba700a708190ab6db62791e43774 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:56 a.m.