Triple
T1260978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo 11 |
E12497
|
entity |
| Predicate | crewQuarantineDuration |
P7618
|
FINISHED |
| Object | 21 days after splashdown |
—
|
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: 21 days after splashdown | Statement: [Apollo 11, crewQuarantineDuration, 21 days after splashdown]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crewQuarantineDuration Context triple: [Apollo 11, crewQuarantineDuration, 21 days after splashdown]
-
A.
missionDuration
Indicates the length of time over which a mission or operation takes place from start to finish.
-
B.
missionDurationType
Indicates the classification of a mission’s length or time span (e.g., short-term, long-term, extended).
-
C.
typicalDurationDays
chosen
Indicates the usual or expected number of days that an associated event, process, or state typically lasts.
-
D.
missionDurationCapability
Indicates the length of time an entity is capable of sustaining or performing a mission or operation.
-
E.
missionDurationToLastContact
Indicates the length of time from the mission’s start until the most recent (or final) communication contact.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a4bfc64e648190b9c4f980eb8168aa |
completed | March 1, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69a4bb6eefbc81908dddd7d2ef368186 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:50 p.m.