Triple
T32023954
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pound–Rebka experiment |
E817767
|
entity |
| Predicate | confirmationType |
P4965
|
FINISHED |
| Object | terrestrial test |
—
|
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: terrestrial test | Statement: [Pound–Rebka experiment, confirmationType, terrestrial test]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: confirmationType Context triple: [Pound–Rebka experiment, confirmationType, terrestrial test]
-
A.
confirmationMethod
chosen
Indicates the means or process by which something is verified, validated, or confirmed as true or accepted.
-
B.
confirmationOutcome
Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
-
C.
confirmedBy
Indicates that one entity validates, approves, or verifies the truth, accuracy, or occurrence of another entity or event.
-
D.
confirmationRequirement
Indicates that an action, decision, or change is contingent on receiving explicit confirmation from a specified party or process.
-
E.
confirmationDocument
Indicates that there exists a document serving as formal confirmation or verification of an action, event, or agreement between entities.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6ffbad8848190867c2988c0ceb84f |
completed | May 3, 2026, 7:56 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
Created at: May 1, 2026, 12:17 a.m.