Triple
T26280598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellenistic science |
E660689
|
entity |
| Predicate | developsField |
P165030
|
FINISHED |
| Object | astronomy |
—
|
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: astronomy | Statement: [Hellenistic science, developsField, astronomy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developsField Context triple: [Hellenistic science, developsField, astronomy]
-
A.
developedInField
Indicates that an entity (such as a method, theory, or technology) was created, formulated, or advanced within a particular academic or professional field.
-
B.
developsWhen
Indicates that one condition, feature, or state comes into existence or forms as a result of another condition, feature, or state.
-
C.
developsDuring
Indicates that one process, condition, or characteristic comes into existence or forms over the course of a specified time period, phase, or event.
-
D.
developmentFor
Indicates that one entity is created, adapted, or advanced specifically for the benefit, use, or purpose of another entity.
-
E.
developmentPillar
Indicates that one entity serves as a fundamental pillar or core focus area supporting the development or growth of another entity.
- 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_69ee812960d081909cff6085cc9fa3a6 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65705a3048190a3728b695ba2ae65 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651a731508190bb0c8c2462eba224 |
completed | May 2, 2026, 7:33 p.m. |
| PDg | Predicate description generation | batch_69f6562ef4e4819082ce6abd41b74dc5 |
completed | May 2, 2026, 7:53 p.m. |
Created at: April 26, 2026, 10 p.m.