Triple
T32431882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chandrayaan-3 propulsion module |
E828745
|
entity |
| Predicate | separationEventDate |
P174074
|
FINISHED |
| Object | 2023-08-17 |
—
|
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: 2023-08-17 | Statement: [Chandrayaan-3 propulsion module, separationEventDate, 2023-08-17]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: separationEventDate Context triple: [Chandrayaan-3 propulsion module, separationEventDate, 2023-08-17]
-
A.
dateOfSeparationAnnouncement
Indicates the date on which the separation between the involved parties was formally announced.
-
B.
separationYear
Indicates the year in which two entities ended or dissolved their relationship or association.
-
C.
separationPeriod
Indicates the duration or interval of time during which two entities are separated from each other.
-
D.
separatedUntil
Indicates that two entities remain apart or not in contact up to a specified time or condition.
-
E.
dateOfCommunitySeparation
Indicates the date on which a community formally separated or split from another community or larger entity.
- 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_69f3491bf298819097b610f772d54a6d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c2af5014819083835a701e683f4f |
completed | May 3, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6eb32c8190bf405b2011fa48f7 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bb344bb48190a8089f29c0063ded |
completed | May 3, 2026, 3:04 a.m. |
Created at: May 1, 2026, 12:55 a.m.