Triple
T4277248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SVC |
E97071
|
entity |
| Predicate | probabilisticOutput |
P12745
|
FINISHED |
| Object | predict_proba |
—
|
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: predict_proba | Statement: [SVC, probabilisticOutput, predict_proba]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: probabilisticOutput Context triple: [SVC, probabilisticOutput, predict_proba]
-
A.
predictedIn
Indicates that something has been forecast, anticipated, or estimated to occur within or as part of a specified context, time, or situation.
-
B.
definesProbability
chosen
Indicates that one entity specifies or assigns the probability value associated with another entity or event.
-
C.
primaryOutput
Indicates that the related entity is the main or principal result, product, or outcome produced by another entity or process.
-
D.
stochastic
Indicates that the relationship or process involves randomness or probabilistic behavior rather than being fully deterministic.
-
E.
hasUncertainty
Indicates that the relationship or value is associated with some level or type of uncertainty rather than being fully definite or precise.
- 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_69b34544be3c819084d1ab82d29f90c5 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3501ef1388190b0c968b069014a59 |
completed | March 12, 2026, 11:45 p.m. |
| PD | Predicate disambiguation | batch_69b347faa45481908c19c29fb906dc92 |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:07 p.m.