Triple
T29768502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trumpler II 3 m |
E753981
|
entity |
| Predicate | brightnessRangeDescription |
P167863
|
FINISHED |
| Object | medium brightness range |
—
|
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: medium brightness range | Statement: [Trumpler II 3 m, brightnessRangeDescription, medium brightness range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brightnessRangeDescription Context triple: [Trumpler II 3 m, brightnessRangeDescription, medium brightness range]
-
A.
brightnessRangeClass
chosen
Indicates the classification of an entity based on the range or interval of its brightness values.
-
B.
brightnessVariation
Indicates a change or fluctuation in the level of brightness of an entity over time or across conditions.
-
C.
lightRange
Indicates the distance or area over which a light source effectively emits or illuminates.
-
D.
brightnessRole
Indicates a relationship where one entity serves a specific role in determining, controlling, or characterizing the brightness of another entity.
-
E.
peakBrightnessBand
Indicates the specific spectral band or wavelength range in which an object's brightness reaches its maximum value.
- 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_69f0ef827ff88190ade56e0b0846b713 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f6745f8354819085a81de5c32dd49e |
completed | May 2, 2026, 10:02 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 8:40 p.m.