Triple
T32259078
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C API |
E824098
|
entity |
| Predicate | exposesBinary |
P174153
|
FINISHED |
| Object | libz3 shared library |
—
|
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: libz3 shared library | Statement: [C API, exposesBinary, libz3 shared library]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exposesBinary Context triple: [C API, exposesBinary, libz3 shared library]
-
A.
exposesTo
Indicates that one entity subjects another entity to contact with or influence from something, typically involving risk, effect, or experience.
-
B.
exposes
Indicates making something visible, known, or vulnerable by removing cover, concealment, or protection.
-
C.
exposesType
Indicates that one entity reveals, makes available, or publicly presents a particular type associated with it.
-
D.
exposedThrough
Indicates that something becomes revealed, accessible, or affected as a result of passing through or being subjected to another thing or medium.
-
E.
exposedAs
Indicates that one entity reveals or publicly identifies another entity as having a hidden, false, or previously concealed role, identity, or nature.
- 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: May 1, 2026, 12:41 a.m.