Triple
T17146747
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rynchops the black skimmer |
E416108
|
entity |
| Predicate | firstPublicationOfContainingWork |
P126289
|
FINISHED |
| Object | 1941 |
—
|
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: 1941 | Statement: [Rynchops the black skimmer, firstPublicationOfContainingWork, 1941]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPublicationOfContainingWork Context triple: [Rynchops the black skimmer, firstPublicationOfContainingWork, 1941]
-
A.
firstPublicationIn
Indicates the initial venue, medium, or context in which a work was first published.
-
B.
originalPublicationOfWholeWork
Indicates that one entity is the original publication in which an entire work was first made publicly available.
-
C.
firstPublicationContext
Indicates the original context or setting (such as venue, medium, or circumstance) in which something was first published.
-
D.
placeOfFirstPublication
Indicates the location where a work was first published or made publicly available.
-
E.
firstPublishedWith
Indicates that an entity was initially published together with another specified entity, sharing the same first publication 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2db20d48190b5d69ccf89f3bc42 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69e3873f62108190966c4e741ebd548d |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:36 a.m.