Triple
T18485246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | V Coronae Australis |
E451671
|
entity |
| Predicate | hasPhotometricObservation |
P26705
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [V Coronae Australis, hasPhotometricObservation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPhotometricObservation Context triple: [V Coronae Australis, hasPhotometricObservation, yes]
-
A.
hasObservationWavelength
Indicates the specific wavelength at which an observation or measurement is made or recorded.
-
B.
hasObservation
chosen
Indicates that an entity records, contains, or is associated with a specific observation or measured instance.
-
C.
hasObservationInstrument
Indicates that a particular instrument or device was used to make or record an observation.
-
D.
hasLightcurveMeasurements
Indicates that an entity has associated lightcurve measurements, representing recorded variations in its brightness over time.
-
E.
hasObservationTarget
Indicates that an observation is directed toward or focused on a particular target 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e531d6502c8190af167b954bf8e989 |
completed | April 19, 2026, 7:49 p.m. |
| PD | Predicate disambiguation | batch_69e469d671088190b619de96ea6f92ab |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:35 a.m.