Triple
T8235664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orcadian Basin |
E192397
|
entity |
| Predicate | hasResearchImportance |
P81001
|
FINISHED |
| Object | Devonian fish evolution |
—
|
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: Devonian fish evolution | Statement: [Orcadian Basin, hasResearchImportance, Devonian fish evolution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchImportance Context triple: [Orcadian Basin, hasResearchImportance, Devonian fish evolution]
-
A.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
B.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
C.
hasCommercialImportance
Indicates that something possesses economic or business value significant enough to impact trade, revenue, or market activity.
-
D.
hasResearchGoal
Indicates that an entity has a specific research objective, aim, or target it is pursuing or designed to address.
-
E.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb782a5e18819096235679f5a644a8 |
completed | March 31, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69cb36b1dea0819091418072501e79c1 |
completed | March 31, 2026, 2:51 a.m. |
| PDg | Predicate description generation | batch_69cb3d6c34708190a987d68529cbb0b3 |
completed | March 31, 2026, 3:20 a.m. |
Created at: March 30, 2026, 5:46 p.m.