Triple
T31141420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicolaus Copernicus Thorunensis terrae motor Solis Caelique stator |
E793795
|
entity |
| Predicate | praisesAs |
P49305
|
FINISHED |
| Object | mover of the Earth |
—
|
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: mover of the Earth | Statement: [Nicolaus Copernicus Thorunensis terrae motor Solis Caelique stator, praisesAs, mover of the Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: praisesAs Context triple: [Nicolaus Copernicus Thorunensis terrae motor Solis Caelique stator, praisesAs, mover of the Earth]
-
A.
typeOfPraise
Indicates a specific kind or category of praise being expressed or applied in a given context.
-
B.
isPraisedIn
Indicates that an entity receives praise, commendation, or positive recognition within a specified context or source.
-
C.
notablePraise
Indicates that one entity has given significant or distinguished praise or commendation to another entity.
-
D.
praisedEntity
chosen
Indicates that one entity expresses approval, admiration, or commendation toward another entity.
-
E.
praisedDeity
Indicates that one entity expressed praise, admiration, or reverence toward a deity.
- 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_69f224d2b3a48190aa9dd26fbf6eab1a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:05 p.m.