Triple
T10915709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 636 |
E257816
|
entity |
| Predicate | PEPNumber |
P96384
|
FINISHED |
| Object | 636 |
—
|
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: 636 | Statement: [PEP 636, PEPNumber, 636]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PEPNumber Context triple: [PEP 636, PEPNumber, 636]
-
A.
opusNumber
Indicates that a creative work is assigned a specific opus number identifying its place within a creator’s catalog or chronological sequence of works.
-
B.
patentNumber
Indicates that a specific patent is identified or referenced by a particular patent number.
-
C.
projectNumber
Indicates a relationship where a specific identifying number is assigned to or associated with a particular project.
-
D.
PSE
Indicates a relationship where one entity is engaged in or associated with a public service or public sector employment role relative to another entity or context.
-
E.
ISONumber
Indicates that an entity is associated with, identified by, or conforms to a specific ISO (International Organization for Standardization) number or standard.
- 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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d77074c77c8190af91369eee11f1b7 |
completed | April 9, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69d70d3f9dc88190a686a8b0dd6a3b21 |
completed | April 9, 2026, 2:21 a.m. |
| PDg | Predicate description generation | batch_69d710400ea88190ac2ed6f0a13d62c1 |
completed | April 9, 2026, 2:34 a.m. |
Created at: April 8, 2026, 9:22 p.m.