Triple
T18564701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Base64 |
E453732
|
entity |
| Predicate | urlSafeVariantReplaces |
P28535
|
FINISHED |
| Object | + with - |
—
|
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: + with - | Statement: [Base64, urlSafeVariantReplaces, + with -]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: urlSafeVariantReplaces Context triple: [Base64, urlSafeVariantReplaces, + with -]
-
A.
replacedWith
Indicates that one entity has been substituted or superseded by another entity, taking over its role, function, or position.
-
B.
replacementName
Indicates that one entity serves as a substitute or successor name for another entity, effectively replacing the original designation.
-
C.
rulesVariantOf
Indicates that one set of rules is a modified or alternative version derived from another set of rules.
-
D.
replacedStandard
chosen
Indicates that one standard has been superseded or taken the place of another standard.
-
E.
weakenedVariantsInclude
Indicates that a set of weakened or attenuated forms of something (e.g., a virus, argument, or feature) contains or encompasses the specified variant.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53afd8114819093b57d86f8213311 |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:42 a.m.