Triple
T17522291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 508 |
E426702
|
entity |
| Predicate | extraExample |
P127793
|
FINISHED |
| Object | requests[security] |
—
|
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: requests[security] | Statement: [PEP 508, extraExample, requests[security]]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extraExample Context triple: [PEP 508, extraExample, requests[security]]
-
A.
centralExample
Indicates that one entity serves as the primary or most representative example of another entity or concept.
-
B.
nonExample
Indicates that something is explicitly identified as not being an example or instance of a given concept, category, or pattern.
-
C.
majorExample
Indicates that one entity serves as a primary or most significant example or instance of another entity.
-
D.
baseExamples
Indicates that something serves as a fundamental or illustrative example for understanding or demonstrating another concept, item, or case.
-
E.
hasExample
Indicates that one entity serves as an instance, illustration, or concrete example 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_69d889de677081909b22d2657b1f0292 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e452d40ee08190b79d8e3d7f1b1272 |
completed | April 19, 2026, 3:58 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f8b9888190aa8a45e09acf4319 |
completed | April 18, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69e3bbb37d148190b7f38599c06594ee |
completed | April 18, 2026, 5:13 p.m. |
Created at: April 10, 2026, 5:49 a.m.