Triple
T663348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fidra |
E12804
|
entity |
| Predicate | designatedFor |
P3344
|
FINISHED |
| Object | breeding seabirds |
—
|
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: breeding seabirds | Statement: [Fidra, designatedFor, breeding seabirds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designatedFor Context triple: [Fidra, designatedFor, breeding seabirds]
-
A.
designatedDayFor
Indicates that a specific day is officially assigned or reserved for a particular purpose, event, or activity.
-
B.
isDesignedFor
Indicates that one entity has been created, planned, or optimized specifically to serve the needs, purposes, or use of another entity.
-
C.
appointedFor
chosen
Indicates that an entity has been officially assigned or designated to perform a specific role, task, or function for another entity or purpose.
-
D.
canBeDesignatedBy
Indicates that one entity is capable of being assigned, labeled, or identified by another entity as its designation.
-
E.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
- 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_69a493355dec819098d4244b2fa34885 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49fd1f0ec819087003d30bbab2fa6 |
completed | March 1, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69a49d153a948190b3ccdc331ed33617 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.