Triple
T3631178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kepler (Martian crater) |
E76958
|
entity |
| Predicate | approvalStatus |
P49674
|
FINISHED |
| Object | adopted |
—
|
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: adopted | Statement: [Kepler (Martian crater), approvalStatus, adopted]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approvalStatus Context triple: [Kepler (Martian crater), approvalStatus, adopted]
-
A.
approvedAt
Indicates the date and time at which an entity received formal approval.
-
B.
approvedBy
Indicates that an action, request, or item has received formal authorization or consent from a specified entity.
-
C.
approvalProcess
Indicates the sequence of steps, decisions, and authorizations required for something to be formally reviewed and approved.
-
D.
approvalMethod
Indicates the method or process by which approval is granted or obtained between entities.
-
E.
approvalRequirement
Indicates that one entity must grant permission or authorization before another entity’s action, decision, or state change can proceed.
- 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_69ad85dc03948190b35b7189e4175bcc |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30136e88190922bb542971b5239 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb8410a5881909c94818d7060b2b0 |
completed | March 8, 2026, 5:56 p.m. |
| PDg | Predicate description generation | batch_69adb902e61c81908f10494f828e260f |
completed | March 8, 2026, 5:59 p.m. |
Created at: March 8, 2026, 3:23 p.m.