Triple
T13179792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AllWISE Reject Table |
E313692
|
entity |
| Predicate | reasonForRejectionIncludes |
P10714
|
FINISHED |
| Object | poor photometric quality |
—
|
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: poor photometric quality | Statement: [AllWISE Reject Table, reasonForRejectionIncludes, poor photometric quality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRejectionIncludes Context triple: [AllWISE Reject Table, reasonForRejectionIncludes, poor photometric quality]
-
A.
reasonForDecline
Indicates the explanation or cause given for why something was rejected, reduced, or not accepted.
-
B.
rejectedBecause
Indicates that one entity refused, dismissed, or did not accept another entity specifically due to a stated reason or cause.
-
C.
reasonForDisqualification
chosen
Indicates the specific cause or justification for which an entity was deemed ineligible or disqualified from consideration or participation.
-
D.
reasonForReversal
Indicates the specific cause or justification for undoing, overturning, or reversing a prior decision, action, or outcome.
-
E.
resultOfRejection
Indicates that something occurs as a consequence or outcome of a prior act of rejection.
- 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bc2c0c88190be357811aa8e828d |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:14 p.m.