Triple
T20888695
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mic |
E514351
|
entity |
| Predicate | associatedConstellationGenitive |
P9993
|
FINISHED |
| Object | Microscopii |
—
|
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: Microscopii | Statement: [Mic, associatedConstellationGenitive, Microscopii]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedConstellationGenitive Context triple: [Mic, associatedConstellationGenitive, Microscopii]
-
A.
relatedConstellation
chosen
Indicates a relationship where one entity is associated with, connected to, or corresponds to a particular constellation.
-
B.
constellationName
Indicates that an entity is identified by the proper name of a constellation.
-
C.
constellationType
Indicates that one entity is classified as a specific type or category of constellation in relation to another entity.
-
D.
constellationFamily
Indicates that one constellation belongs to the same traditional family or grouping of constellations as another.
-
E.
parentConstellation
Indicates that one constellation is the larger or primary constellation within which another constellation is contained or of which it is a part.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d05be4a081908de0d3f5dbe4429a |
completed | April 21, 2026, 1:18 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:46 p.m.