Triple
T5910791
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercury spacecraft |
E131451
|
entity |
| Predicate | reentryProtection |
P67646
|
FINISHED |
| Object | ablative heat shield |
—
|
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: ablative heat shield | Statement: [Mercury spacecraft, reentryProtection, ablative heat shield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reentryProtection Context triple: [Mercury spacecraft, reentryProtection, ablative heat shield]
-
A.
reentryControl
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
B.
reentryProfile
Indicates the specific trajectory and conditions under which an object returns from space through an atmosphere.
-
C.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
D.
reentryDate
Indicates the date on which an entity returns or is admitted again after a prior departure, exit, or release.
-
E.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
- 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_69c008593a44819081a07ae0efe6c574 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c048fc112c8190b905bf561c9de096 |
completed | March 22, 2026, 7:54 p.m. |
| PD | Predicate disambiguation | batch_69c03352208c8190968efed05a9fd416 |
completed | March 22, 2026, 6:22 p.m. |
| PDg | Predicate description generation | batch_69c048fb02a081908e78629e1e283cd0 |
completed | March 22, 2026, 7:54 p.m. |
Created at: March 22, 2026, 3:59 p.m.