Triple
T33080998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DemoSat |
E846506
|
entity |
| Predicate | payloadFunction |
P176106
|
FINISHED |
| Object | mass simulator |
—
|
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: mass simulator | Statement: [DemoSat, payloadFunction, mass simulator]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: payloadFunction Context triple: [DemoSat, payloadFunction, mass simulator]
-
A.
peakFunction
Indicates that a function reaches a maximum (peak) value at a specific point or over a given interval.
-
B.
actualFunction
Indicates that something serves as the real, operative function or role performed in practice, as opposed to a nominal or theoretical one.
-
C.
publicFunction
Indicates that a function or method is accessible from outside its defining scope, module, or class (i.e., it has public visibility).
-
D.
affectedFunction
Indicates that one entity has an impact on, alters, or impairs the operation or behavior of another entity’s function.
-
E.
protocolFunction
Indicates that one entity serves as a function, role, or operation defined within the rules or structure of a particular protocol 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_69f34954d46c8190a04a159cc5f99efd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6db6af1d88190989810182354d60f |
completed | May 3, 2026, 5:21 a.m. |
| PD | Predicate disambiguation | batch_69f6d82d068c8190940a3200ed760e38 |
completed | May 3, 2026, 5:07 a.m. |
| PDg | Predicate description generation | batch_69f6db6a38d881909ecc75cc527910f2 |
completed | May 3, 2026, 5:21 a.m. |
Created at: May 1, 2026, 1:26 a.m.