Triple
T13538550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Habitation Module |
E323322
|
entity |
| Predicate | locationWhenDeployed |
P82760
|
FINISHED |
| Object | lunar orbit |
—
|
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: lunar orbit | Statement: [International Habitation Module, locationWhenDeployed, lunar orbit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locationWhenDeployed Context triple: [International Habitation Module, locationWhenDeployed, lunar orbit]
-
A.
deploymentLocation
chosen
Indicates the place or environment where something (such as a system, resource, or component) is deployed or put into operational use.
-
B.
platformLocation
Indicates the spatial position or placement of a platform relative to a reference point or environment.
-
C.
locationWhenGiven
Indicates the place where an entity is located at the time it is given or transferred to another entity.
-
D.
operationLocation
Indicates the place or site where an operation, activity, or process is carried out.
-
E.
locatedIn
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
- 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_69d8076776248190bdf0d4fa1f85a5fc |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbafd7ad9481908fe1d7ffcf8fab71 |
completed | April 12, 2026, 2:44 p.m. |
| PD | Predicate disambiguation | batch_69dbae1046c48190b4ee98c6c9cb9d85 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:45 p.m.