Triple
T12598968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pioneer 0 |
E300806
|
entity |
| Predicate | launchAttemptNumber |
P105636
|
FINISHED |
| Object | first U.S. lunar probe attempt |
—
|
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: first U.S. lunar probe attempt | Statement: [Pioneer 0, launchAttemptNumber, first U.S. lunar probe attempt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: launchAttemptNumber Context triple: [Pioneer 0, launchAttemptNumber, first U.S. lunar probe attempt]
-
A.
rescueAttemptNumber
Indicates the ordinal count of distinct attempts made to carry out a rescue in a given rescue situation or operation.
-
B.
completionAttemptsBy
Indicates that a specific entity’s completion attempts are attributed to or performed by another entity.
-
C.
attemptLimit
Indicates a restriction on how many times an action or operation may be attempted before it is stopped or blocked.
-
D.
numberOfTakeoffAttempts
Indicates the count of times a takeoff has been attempted for the given entity or event.
-
E.
triedAt
Indicates that an attempt to perform an action or achieve an outcome occurred at a specific time or place.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9559458dc8190bc4d6e697e99d70e |
completed | April 10, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69d9541894fc8190a0c3706a414279f0 |
completed | April 10, 2026, 7:48 p.m. |
| PDg | Predicate description generation | batch_69d95590a5e08190842b988531cf2921 |
completed | April 10, 2026, 7:54 p.m. |
Created at: April 9, 2026, 5:09 p.m.