Triple
T23188736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beta Canis Minoris |
E579669
|
entity |
| Predicate | hasPhotometricSystem |
P62581
|
FINISHED |
| Object | Johnson V |
—
|
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: Johnson V | Statement: [Beta Canis Minoris, hasPhotometricSystem, Johnson V]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotometricSystem Context triple: [Beta Canis Minoris, hasPhotometricSystem, Johnson V]
-
A.
photometricSystem
chosen
Indicates the photometric measurement system or filter set used when observing or recording a quantity.
-
B.
hasPhotometry
Indicates that an entity possesses or is associated with photometric data or measurements.
-
C.
hasSelenographicCoordinateSystem
Indicates that something is associated with or defined using a coordinate system based on the Moon’s (selenographic) latitude and longitude.
-
D.
hasTristimulusValue
Indicates that an entity is associated with a specific set of three numerical components representing its color in a tristimulus color space.
-
E.
hasProjectionSystem
Indicates that one entity uses or is defined by a particular coordinate or map projection system associated with another entity.
- 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_69e245ff8000819090d12008805315b7 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18fd592248190a7e705c554885cd1 |
completed | April 29, 2026, 4:57 a.m. |
| PD | Predicate disambiguation | batch_69ef8a041c0081909afb670d17a5aaba |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4:05 p.m.