Triple
T28599838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiangong-2 |
E723877
|
entity |
| Predicate | experiments |
P163489
|
FINISHED |
| Object | space medicine experiments |
—
|
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: space medicine experiments | Statement: [Tiangong-2, experiments, space medicine experiments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: experiments Context triple: [Tiangong-2, experiments, space medicine experiments]
-
A.
conductedExperimentsIn
chosen
Indicates that an entity performed or carried out experiments within a specified location or context.
-
B.
experiment
Indicates that an entity conducts, participates in, or is the subject of a controlled test or trial to observe outcomes or validate hypotheses.
-
C.
numberOfExperiments
Indicates the total count of experiments associated with or performed in a given context or entity.
-
D.
showedInExperiments
Indicates that something was demonstrated or observed to occur within the context of experiments.
-
E.
notableExperiment
Indicates that an entity is recognized for having conducted or been the subject of a particularly important or influential experiment.
- 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_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 4:23 a.m.