Triple
T7994168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constellation program |
E186080
|
entity |
| Predicate | includedISSSupport |
P80234
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Constellation program, includedISSSupport, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includedISSSupport Context triple: [Constellation program, includedISSSupport, yes]
-
A.
supportedIn
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
B.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
supportedAs
Indicates that one entity is accepted, recognized, or treated as being in the role, type, or representation of another entity.
-
D.
issueIncludes
Indicates that an issue or problem encompasses, contains, or involves a specified element, component, or sub-issue as part of its scope.
-
E.
tieneSoporte
Indicates that one entity provides support, backing, or a supporting structure for another entity.
- 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_69ca829c6c308190ab05b43d234c52b2 |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3c73ba388190bcedc29fbdd22f3c |
completed | March 31, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69cb0483d3b48190b250c7603d747bca |
completed | March 30, 2026, 11:17 p.m. |
| PDg | Predicate description generation | batch_69cb14bbbacc81909c6cf8ec35314bbb |
completed | March 31, 2026, 12:26 a.m. |
Created at: March 30, 2026, 5:16 p.m.