Triple
T36625509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMT-COMP |
E904157
|
entity |
| Predicate | resultsAre |
P28576
|
FINISHED |
| Object | publicly available |
—
|
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: publicly available | Statement: [SMT-COMP, resultsAre, publicly available]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultsAre Context triple: [SMT-COMP, resultsAre, publicly available]
-
A.
result
Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
-
B.
resultDetermination
Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
-
C.
resultUsage
Indicates how the outcome or result of an action, process, or event is used, applied, or consumed in relation to another entity or context.
-
D.
resultsReportedAs
Indicates that the outcomes or findings of an activity, process, or evaluation are communicated or documented in a specified form, format, or medium.
-
E.
knownResult
chosen
Indicates that the outcome or consequence of an action, process, or event is already determined and available.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fd9ff026a48190bfec33deeb3b2c43 |
completed | May 8, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69fd97d805bc8190ba12f429d3ad04c7 |
completed | May 8, 2026, 7:59 a.m. |
Created at: May 3, 2026, 4:11 p.m.