Triple
T30465413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zeta Centauri |
E775122
|
entity |
| Predicate | hasNakedEyeVisibilityFrom |
P20410
|
FINISHED |
| Object | Australia |
—
|
NE NERFINISHED |
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: Australia | Statement: [Zeta Centauri, hasNakedEyeVisibilityFrom, Australia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNakedEyeVisibilityFrom Context triple: [Zeta Centauri, hasNakedEyeVisibilityFrom, Australia]
-
A.
visibleToNakedEye
chosen
Indicates that something can be perceived directly without the aid of optical instruments such as telescopes, microscopes, or binoculars.
-
B.
canBeSeenFromEarthWith
Indicates that one entity is visible from Earth using the specified instrument, method, or observational aid.
-
C.
visibleFromEarth
Indicates that the object can be observed from Earth, either with the naked eye or with appropriate instruments, under suitable viewing conditions.
-
D.
visibleInSmallTelescope
Indicates that the object can be seen using a small telescope under typical observing conditions.
-
E.
observationalVisibility
Indicates that one entity is able to observe or visually perceive another entity under given conditions.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 8:11 p.m.