Triple
T2138968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apollo–Soyuz Test Project |
E46717
|
entity |
| Predicate | undockingDate |
P37019
|
FINISHED |
| Object | 1975-07-19 |
—
|
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: 1975-07-19 | Statement: [Apollo–Soyuz Test Project, undockingDate, 1975-07-19]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: undockingDate Context triple: [Apollo–Soyuz Test Project, undockingDate, 1975-07-19]
-
A.
decommissionedDate
Indicates the date on which an entity was formally taken out of service or retired from active use.
-
B.
landingDate
Indicates the date on which an entity arrives at or touches down on a specified destination or surface.
-
C.
decommissioningStartDate
Indicates the date on which the process of taking an asset or system out of active service is initiated.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
launchDate
Indicates the date on which an entity (such as a product, service, or project) is officially released or made available.
- 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_69a88a174ab48190a5db20c132e5dccf |
completed | March 4, 2026, 7:37 p.m. |
| NER | Named-entity recognition | batch_69abbf74147c81908793c3694894f94a |
completed | March 7, 2026, 6:02 a.m. |
| PD | Predicate disambiguation | batch_69abbd96a3b0819081efbfef975e1513 |
completed | March 7, 2026, 5:54 a.m. |
| PDg | Predicate description generation | batch_69abbf71edf08190add69022aabfd49d |
completed | March 7, 2026, 6:02 a.m. |
Created at: March 4, 2026, 7:44 p.m.