Triple
T37315563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dome of Stars |
E926322
|
entity |
| Predicate | hadNotableFeature |
P642
|
FINISHED |
| Object | great dome |
—
|
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: great dome | Statement: [Dome of Stars, hadNotableFeature, great dome]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadNotableFeature Context triple: [Dome of Stars, hadNotableFeature, great dome]
-
A.
hasNotableFeature
chosen
Indicates that an entity possesses a specific characteristic, trait, or attribute that is considered significant or noteworthy.
-
B.
noFeature
Indicates that an entity lacks a particular feature, attribute, or characteristic that might otherwise be present.
-
C.
hasNotableHero
Indicates that an entity is associated with a particularly distinguished or prominent hero.
-
D.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
-
E.
hasNotabilityLevel
Indicates that an entity possesses a specified degree or rank of prominence, importance, or recognition relative to others.
- 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_69f76eb28af88190b093b32e3fd614ab |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb78cbef988190b8f79d946b46e6b2 |
completed | May 6, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69fb5a9ac5a08190b24ef308963fc52b |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.