Triple
T37761211
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gliese 581h |
E941276
|
entity |
| Predicate | dataReanalysis |
P96786
|
FINISHED |
| Object | failed to confirm planet |
—
|
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: failed to confirm planet | Statement: [Gliese 581h, dataReanalysis, failed to confirm planet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataReanalysis Context triple: [Gliese 581h, dataReanalysis, failed to confirm planet]
-
A.
resourceHistoricallyExtracted
Indicates that a resource was extracted from a location or entity during some period in the past, but not necessarily in the present.
-
B.
data
chosen
Indicates that one entity serves as informational content, measurements, or recorded values associated with another entity.
-
C.
analysisMode
Indicates that an entity is operating under a specific analytical configuration or method for processing or evaluating information.
-
D.
dataAre
Indicates that one entity serves as the data or informational content associated with another entity.
-
E.
historicalDatum
Indicates that something is a specific piece of information or record about a past event, condition, or state.
- 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_69f76ee3251881909bb4451aad50752b |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef947488190837b9cc9d8c9bde9 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:19 p.m.