Triple
T10638294
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Planetario Galileo Galilei |
E250648
|
entity |
| Predicate | has3DProjectionSystem |
P95107
|
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: [Planetario Galileo Galilei, has3DProjectionSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: has3DProjectionSystem Context triple: [Planetario Galileo Galilei, has3DProjectionSystem, yes]
-
A.
has3DVersion
Indicates that an entity has a corresponding three-dimensional (3D) version or representation.
-
B.
stereoscopic3D
Indicates that the subject is presented or perceived using stereoscopic 3D techniques, creating a depth effect by delivering slightly different images to each eye.
-
C.
has3DGlasses
Indicates that an entity possesses or is equipped with 3D glasses.
-
D.
supports3DTransforms
Indicates that one entity provides or is compatible with three-dimensional transform capabilities for another entity or within a given context.
-
E.
hasViewingAngles
Indicates that one entity possesses or is characterized by specific viewing angles relative to another entity or reference frame.
- 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_69d6aa5993448190a493b790b8f85010 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfaf12188190a5774d4d64674653 |
completed | April 8, 2026, 11:07 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 9:04 p.m.