Triple
T30809475
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaplygin T |
E784602
|
entity |
| Predicate | surfaceProcessOrigin |
P51498
|
FINISHED |
| Object | impact event |
—
|
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: impact event | Statement: [Chaplygin T, surfaceProcessOrigin, impact event]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: surfaceProcessOrigin Context triple: [Chaplygin T, surfaceProcessOrigin, impact event]
-
A.
originProcess
chosen
Indicates the process, activity, or mechanism from which an entity, condition, or outcome originally arises or is produced.
-
B.
surfaceSystem
Indicates that one entity serves as the outer or exposed system or layer upon which another entity is situated or with which it directly interacts.
-
C.
surfaceRecord
Indicates that an entity documents or presents information about the external aspects or observable features of another entity or phenomenon.
-
D.
surfaceAccess
Indicates that one entity provides a means for another entity to reach, enter, or interact with a surface or outer layer.
-
E.
surfaceState
Indicates the physical condition or status of a surface, such as its texture, cleanliness, damage, or treatment at a given time.
- 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_69f224b3a7ec819096939414d103e31e |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6904138088190ad4209ce7caa4ea3 |
completed | May 3, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69f68b7d2794819092fef8a63f4f3de8 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 29, 2026, 8:43 p.m.