Triple
T432704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | METI |
E9746
|
entity |
| Predicate | raisesQuestion |
P13891
|
FINISHED |
| Object | who should decide to send messages from Earth |
—
|
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: who should decide to send messages from Earth | Statement: [METI, raisesQuestion, who should decide to send messages from Earth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: raisesQuestion Context triple: [METI, raisesQuestion, who should decide to send messages from Earth]
-
A.
centralQuestion
Indicates that something is the main issue, problem, or inquiry around which a discussion, work, or investigation is focused.
-
B.
questionType
Indicates the specific category or kind of question that an item, query, or prompt belongs to.
-
C.
canRaise
Indicates that one entity has the ability or authority to increase, elevate, or lift another entity (such as a value, object, or status).
-
D.
answeredBy
Indicates that a question, request, or problem is responded to or resolved by a particular entity.
-
E.
firstRaisedBy
Indicates that one entity was the earliest or original source to bring up, introduce, or initiate the referenced issue, idea, or topic in relation to another entity.
- F. None of above. chosen
Provenance (4 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_69a2e801e1d48190b505d1dd336b52ac |
completed | Feb. 28, 2026, 1:05 p.m. |
| NER | Named-entity recognition | batch_69a2ef084840819080653004b674cba8 |
completed | Feb. 28, 2026, 1:35 p.m. |
| PD | Predicate disambiguation | batch_69a2edd9264c8190b92f9a50348e5541 |
completed | Feb. 28, 2026, 1:30 p.m. |
| PDg | Predicate description generation | batch_69a2eeb93584819082f23eff13e17c4f |
completed | Feb. 28, 2026, 1:33 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.