Triple
T18776076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stephenson 2-18 |
E459136
|
entity |
| Predicate | hasHighInfraredBrightness |
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: [Stephenson 2-18, hasHighInfraredBrightness, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHighInfraredBrightness Context triple: [Stephenson 2-18, hasHighInfraredBrightness, true]
-
A.
supportsInfraredConnectivity
Indicates that one entity provides or enables infrared-based communication or data transfer capabilities for another entity.
-
B.
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.
-
C.
intrinsicBrightness
Indicates the inherent level of light or luminosity an entity possesses, independent of external factors or observation conditions.
-
D.
numberOfInfraredChannels
Indicates the count of distinct infrared channels associated with or supported by an entity.
-
E.
isBright
Indicates that an entity emits or reflects a high level of light, making it visually intense or luminous.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5933b912481908bfd97216eacb257 |
completed | April 20, 2026, 2:45 a.m. |
| PD | Predicate disambiguation | batch_69e48d1126e4819099607837ed5aadca |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:52 a.m.