Triple
T17522133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PEP 425 platform compatibility tags |
E426699
|
entity |
| Predicate | abiTagExample |
P127788
|
FINISHED |
| Object | cp39 |
—
|
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: cp39 | Statement: [PEP 425 platform compatibility tags, abiTagExample, cp39]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: abiTagExample Context triple: [PEP 425 platform compatibility tags, abiTagExample, cp39]
-
A.
providesABI
Indicates that one entity supplies or makes available an Application Binary Interface (ABI) for another entity to use.
-
B.
iauCode
Indicates the standardized code assigned by the International Astronomical Union (IAU) to uniquely identify an astronomical object or entity.
-
C.
tagType
Indicates the classification or category assigned to a tag, specifying what kind of tag it is or how it should be interpreted.
-
D.
interactionWithEIP
Indicates a relationship where an entity engages in or is involved in some form of interaction with an EIP (e.g., using, modifying, or communicating about it).
-
E.
swiftCode
Indicates that a financial institution is identified or associated with a specific SWIFT/BIC code used for international banking transactions.
- 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_69e452d2f79881909556894728e255ab |
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.