Triple
T37532970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | σ Herculis |
E933108
|
entity |
| Predicate | showsInfraredExcess |
P29858
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [σ Herculis, showsInfraredExcess, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsInfraredExcess Context triple: [σ Herculis, showsInfraredExcess, true]
-
A.
infraredExcess
chosen
Indicates that an object emits more infrared radiation than expected from its visible or thermal continuum, typically due to additional dust or circumstellar material.
-
B.
changesInfraredTransmittanceNear
Indicates that one entity alters the infrared light transmittance properties of another entity in its vicinity.
-
C.
isBrightGiantIn
Indicates that an entity is a bright giant star located within a specified astronomical region or system.
-
D.
supportsInfraredConnectivity
Indicates that one entity provides or enables infrared-based communication or data transfer capabilities for another entity.
-
E.
visibleInLongExposureImages
Indicates that the subject can be detected or seen when images are captured using long exposure photography settings.
- 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_69f76ec8862c8190bfa24145f5480642 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbacaf54648190811ea33b34907e8e |
completed | May 6, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_69fba883f770819091059c6f6c6af9f7 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:17 p.m.