Triple
T24425101
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Raphus cucullatus |
E615832
|
entity |
| Predicate | firstEuropeanRecord |
P155876
|
FINISHED |
| Object | late 16th century |
—
|
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: late 16th century | Statement: [Raphus cucullatus, firstEuropeanRecord, late 16th century]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstEuropeanRecord Context triple: [Raphus cucullatus, firstEuropeanRecord, late 16th century]
-
A.
hasEuropeanRecord
Indicates that an entity holds or is associated with a record or best performance recognized at the European level.
-
B.
firstRecordedWith
Indicates that an entity’s earliest known or documented occurrence is associated with a specified context, source, or accompanying entity.
-
C.
internationalRecord
Indicates that an entity holds or has achieved a recognized performance, participation, or achievement record at the international level.
-
D.
firstRecordingDate
Indicates the date on which an entity’s first recording (e.g., audio, video, or similar captured performance) was made.
-
E.
firstEuropeanPerformancePlace
Indicates the location where something (such as a work, event, or performance) was first performed in Europe.
- 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_69e2d7eadb248190a867130fe45f0388 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a62644819089d01ec90e8bee3c |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
| PDg | Predicate description generation | batch_69f2915233c48190a181c8c1924e892c |
completed | April 29, 2026, 11:16 p.m. |
Created at: April 18, 2026, 2:15 a.m.