Triple
T816058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PyPy |
E17653
|
entity |
| Predicate | isDropInReplacementFor |
P5887
|
FINISHED |
| Object | CPython in many use cases |
—
|
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: CPython in many use cases | Statement: [PyPy, isDropInReplacementFor, CPython in many use cases]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDropInReplacementFor Context triple: [PyPy, isDropInReplacementFor, CPython in many use cases]
-
A.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
isSupportedBy
Indicates that an entity is upheld, sustained, or enabled by another entity, which provides necessary assistance, resources, or justification.
-
C.
isVersionOf
Indicates that one entity is a particular version, edition, or variant derived from another entity.
-
D.
backwardCompatibleWith
Indicates that one entity can correctly interpret, use, or function with data, interfaces, or behavior designed for an earlier version of another entity.
-
E.
replacedSystemUsedUntil
Indicates that one system was used up until it was replaced by another system.
- F. None of above.
Provenance (3 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_69a4937bcaac8190a322524ac6f45a5a |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4ab5157b08190b6c8f2fd455f261e |
completed | March 1, 2026, 9:10 p.m. |
| PD | Predicate disambiguation | batch_69a4aa756920819080ae82948974c876 |
completed | March 1, 2026, 9:07 p.m. |
Created at: March 1, 2026, 7:38 p.m.