Triple
T23906611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LGS 3 |
E601214
|
entity |
| Predicate | hasCentralSurfaceBrightness |
P66832
|
FINISHED |
| Object | very low |
—
|
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: very low | Statement: [LGS 3, hasCentralSurfaceBrightness, very low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralSurfaceBrightness Context triple: [LGS 3, hasCentralSurfaceBrightness, very low]
-
A.
surfaceBrightness_V_mag_per_arcsec2
Indicates the surface brightness of an object measured in V-band magnitudes per square arcsecond, relating its emitted light to the area it covers on the sky.
-
B.
hasCentralIntensity
chosen
Indicates that something possesses a specific value or measure of intensity at its central point or core region.
-
C.
hasVeryLowSurfaceBrightness
Indicates that an entity exhibits an extremely faint or low level of brightness across its visible surface.
-
D.
intrinsicBrightness
Indicates the inherent level of light or luminosity an entity possesses, independent of external factors or observation conditions.
-
E.
apparentBrightness
Indicates how bright one object appears from the perspective or location of another, regardless of its actual intrinsic luminosity.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce91144c8190b894e25a45dfd7c9 |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:35 p.m.