Triple
T22355595
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achernar |
E552642
|
entity |
| Predicate | isDifficultToSeeFrom |
P147891
|
FINISHED |
| Object | most of the Northern Hemisphere |
—
|
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: most of the Northern Hemisphere | Statement: [Achernar, isDifficultToSeeFrom, most of the Northern Hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDifficultToSeeFrom Context triple: [Achernar, isDifficultToSeeFrom, most of the Northern Hemisphere]
-
A.
isDifficultToObserveInVisible
Indicates that the subject cannot be easily detected or studied using visible-wavelength (optical) observations.
-
B.
isEasierToSeeThan
Indicates that one entity is more visually noticeable or discernible than another under comparable viewing conditions.
-
C.
visibilityFromSea
Indicates that something can be seen or is visually detectable when viewed from the sea.
-
D.
canBeSeenWith
Indicates that two entities are observable together in the same context, setting, or time.
-
E.
isDifficultToAccessBecauseOf
Indicates that something is hard to reach, obtain, or use due to a specified obstacle, condition, or circumstance.
- 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_69e11e4a0ad08190a385b4d343cf6524 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f157cf94508190b0f2c63ddfecb813 |
completed | April 29, 2026, 12:58 a.m. |
| PD | Predicate disambiguation | batch_69e7300c20088190a59e5bf9e70384f3 |
completed | April 21, 2026, 8:06 a.m. |
| PDg | Predicate description generation | batch_69e7342ce08c8190bc0a7085f4a952e7 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 8:44 p.m.