Triple
T31081054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NaCl API |
E792093
|
entity |
| Predicate | abstractsDetail |
P170725
|
FINISHED |
| Object | key sizes |
—
|
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: key sizes | Statement: [NaCl API, abstractsDetail, key sizes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abstractsDetail Context triple: [NaCl API, abstractsDetail, key sizes]
-
A.
abstracts
Indicates that one entity generalizes, conceptualizes, or derives an abstract representation from another entity or set of details.
-
B.
abstractsResource
Indicates that one entity represents or summarizes the essential aspects of another entity, omitting certain details while capturing its core characteristics.
-
C.
abstractsFromUsers
Indicates that something omits, hides, or generalizes away details specifically related to users.
-
D.
publicationDetail
Indicates the specific publication-related information associated with an entity, such as how, where, or in what form it is published.
-
E.
includesAbstract
Indicates that one entity contains or incorporates the abstract or summary section of 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_69f224ccdbbc81909b0cdb4cc2d70c7a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690f13d7481908ddfefe95df2a1c2 |
completed | May 3, 2026, 12:04 a.m. |
| PDg | Predicate description generation | batch_69f6938244648190a553b532387b812c |
completed | May 3, 2026, 12:14 a.m. |
Created at: April 29, 2026, 9:02 p.m.