Triple
T24435049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Geospiza fortis |
E616101
|
entity |
| Predicate | studySite |
P156124
|
FINISHED |
| Object | Daphne Major |
—
|
NE NERFINISHED |
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: Daphne Major | Statement: [Geospiza fortis, studySite, Daphne Major]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: studySite Context triple: [Geospiza fortis, studySite, Daphne Major]
-
A.
studiesFor
Indicates that one entity engages in studying or academic preparation with the purpose of achieving or supporting another entity (such as a goal, exam, or qualification).
-
B.
servesAsTeachingSiteFor
Indicates that one entity functions as a location or institution where teaching, training, or educational activities are conducted for another entity.
-
C.
studyMethods
Indicates that an entity uses or engages in particular methods or techniques for studying.
-
D.
studType
Indicates a relationship where an entity is classified as a particular type or category of stud (e.g., a specific kind of fastener or structural element).
-
E.
studDuty
Indicates that an entity has a duty, responsibility, or obligation related to studying or academic work.
- 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_69e2d7ec44b081909ccaf1f3bbec0641 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f297855fd08190904eedd2666d9622 |
completed | April 29, 2026, 11:43 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:16 a.m.