Triple
T26300366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Perinaldo |
E661537
|
entity |
| Predicate | hasAstronomicalHeritage |
P62338
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Perinaldo, hasAstronomicalHeritage, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstronomicalHeritage Context triple: [Perinaldo, hasAstronomicalHeritage, yes]
-
A.
isLinkedToAstronomy
chosen
Indicates that something has a connection or relevant association to the field or study of astronomy.
-
B.
astronomicalAchievement
Indicates an entity has accomplished a notable or significant feat in the field of astronomy or space exploration.
-
C.
hasAstroObjectNamedAfter
Indicates that one entity has an astronomical object (such as a star, planet, asteroid, or other celestial body) named in honor of or after another entity.
-
D.
hasIAUName
Indicates that an entity is assigned an official name as recognized by the International Astronomical Union (IAU).
-
E.
hasAstronomicalFeature
Indicates that an entity possesses, contains, or is characterized by a specific astronomical feature (such as a star, planet, crater, or other celestial structure).
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f65aa07c048190a5df30d53d8f0cf5 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f659cc571c819097e51e531961d812 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 26, 2026, 10:15 p.m.