Triple
T13127113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base 33 |
E311871
|
entity |
| Predicate | likelyFunctions |
P14773
|
FINISHED |
| Object | support to space operations |
—
|
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: support to space operations | Statement: [Base 33, likelyFunctions, support to space operations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: likelyFunctions Context triple: [Base 33, likelyFunctions, support to space operations]
-
A.
possibleFunction
chosen
Indicates that an entity may serve, or is capable of serving, a particular function or role, without asserting that it actually does so.
-
B.
likelySource
Indicates that one entity is considered the probable origin or cause of another entity or event.
-
C.
likelyComposition
Indicates that one entity is probably a component or constituent part of another entity, though this compositional relationship is uncertain or inferred rather than definite.
-
D.
possibleRelative
Indicates a relationship where one entity may be related to another by family or kinship, but the exact nature of the relationship is uncertain or not fully established.
-
E.
functionHypothesis
Indicates that an entity is proposed or assumed to serve as a function or functional explanation for another entity or phenomenon.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819aac388190b59bf43cc6a49d0c |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.