Triple
T20412929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phobos 2 |
E500633
|
entity |
| Predicate | communicationLossDate |
P54757
|
FINISHED |
| Object | 1989-03-27 |
—
|
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: 1989-03-27 | Statement: [Phobos 2, communicationLossDate, 1989-03-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationLossDate Context triple: [Phobos 2, communicationLossDate, 1989-03-27]
-
A.
communicatedOn
Indicates that a communication event took place on a specific date or time.
-
B.
reasonForContactLoss
Indicates the cause or circumstance that led to the loss or termination of contact between entities.
-
C.
timeOfLossOfContactUTC
chosen
Indicates the specific time, expressed in Coordinated Universal Time (UTC), at which contact with an entity was lost.
-
D.
dateOfLoss
Indicates the specific date on which a loss event (such as damage, theft, or other covered incident) occurred.
-
E.
lostFunctionDate
Indicates the date on which a function, capability, or operational role ceased to be active or usable.
- 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_69e0b4a935588190b9446a99b37ced44 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67a417f208190be9bc11650ee0a87 |
completed | April 20, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69e5765d7cb48190adec18d6d1e3d263 |
completed | April 20, 2026, 12:42 a.m. |
Created at: April 16, 2026, 11:30 a.m.