Triple
T28599846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiangong-2 |
E723877
|
entity |
| Predicate | controlledReentry |
P43711
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Tiangong-2, controlledReentry, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlledReentry Context triple: [Tiangong-2, controlledReentry, true]
-
A.
reentryProtection
Indicates that an entity is safeguarded against harmful effects or risks associated with reentering a system, environment, or jurisdiction.
-
B.
reentryControl
chosen
Indicates that an entity manages or regulates the process of returning or re-entering into a system, environment, or state.
-
C.
controlledFor
Indicates that the influence or effect of a specified factor has been accounted for or neutralized when assessing the relationship between other variables or entities.
-
D.
controlledIn
Indicates that one entity exercised control, authority, or governance over another entity within a specific context or domain.
-
E.
notReentrant
Indicates that the associated function or operation cannot be safely invoked again (re-entered) before a previous invocation has fully completed.
- 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_69f01d80b1908190980594837604b8c7 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 28, 2026, 4:23 a.m.