Triple
T35690969
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ison |
E1031290
|
entity |
| Predicate | hasAstrographicalRegion |
P9997
|
FINISHED |
| Object | Anoat sector |
—
|
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: Anoat sector | Statement: [Ison, hasAstrographicalRegion, Anoat sector]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAstrographicalRegion Context triple: [Ison, hasAstrographicalRegion, Anoat sector]
-
A.
hasSelenographicRegion
Indicates that something is associated with or located within a specific region on the Moon’s surface.
-
B.
locatedInSkyRegion
chosen
Indicates that an entity is situated within or associated with a specific region or area of the sky.
-
C.
isAsterismOf
Indicates that one or more stars collectively form or belong to a specific asterism.
-
D.
hasOrbitalRegion
Indicates that one entity occupies, lies within, or is associated with a specific orbital zone or region around another body.
-
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_69f76e0c73ec819080ab60a9e2f5f1f6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fd3a69f1e08190a11aed015bff0858 |
completed | May 8, 2026, 1:20 a.m. |
| PD | Predicate disambiguation | batch_69fd39124180819080ca7911d3515d6d |
completed | May 8, 2026, 1:14 a.m. |
Created at: May 3, 2026, 4:05 p.m.