Triple
T3644120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Epitome Astronomiae Copernicanae |
E77256
|
entity |
| Predicate | expoundsTheory |
P42609
|
FINISHED |
| Object | heliocentric model |
—
|
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: heliocentric model | Statement: [Epitome Astronomiae Copernicanae, expoundsTheory, heliocentric model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expoundsTheory Context triple: [Epitome Astronomiae Copernicanae, expoundsTheory, heliocentric model]
-
A.
presentsTheory
Indicates that one entity formally puts forward or explains a theory to another entity or audience.
-
B.
developsTheory
Indicates that one entity formulates, elaborates, or advances a theoretical framework or explanation concerning another entity.
-
C.
appliesTheory
Indicates that an entity uses or implements a particular theory in analyzing, explaining, or addressing something.
-
D.
theorized
Indicates that one entity has proposed or developed a theoretical explanation or hypothesis about another entity or phenomenon.
-
E.
theoreticalText
chosen
Indicates that one entity is a theoretical or conceptual written work about, or used as a basis for understanding, the other entity.
- F. None of above.
Provenance (3 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_69ad85de1b988190a45f8dbfebc806fc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc35c28908190b253f4835918a2b4 |
completed | March 8, 2026, 6:43 p.m. |
| PD | Predicate disambiguation | batch_69adb8445b2c8190ab07f6ad4e010d0e |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.